Crates.io | envset |
lib.rs | envset |
version | 0.1.17 |
source | src |
created_at | 2024-09-06 22:15:51.791501 |
updated_at | 2024-10-09 03:54:36.809338 |
description | A command-line tool for setting environment variables in a .env file |
homepage | https://github.com/schpet/envset |
repository | https://github.com/schpet/envset |
max_upload_size | |
id | 1366657 |
size | 80,560 |
envset
is a CLI for setting environment variables in .env files.
this is something you may have never considered needing a specialized tool for. and you don't. but just like updating a git config it's more fun with a command.
currently available on homebrew and crates.io
brew install schpet/tap/envset
cargo install envset
# basic usage, FYI that it prints a diff of the changes to stdout
envset KEY1=value1 KEY2=value2
# some env vars are normally very annoying to set, like json or multiline strings.
# but envset has your back!
envset JSON="$(cat credentials.json)" PRIVATE_KEY="$(openssl genrsa -out /dev/stdout 2048)"
# pipe in stdin, useful for copying stuff from one env to another
echo -e "KEY1=value1\nKEY2=value2" | envset
# heroku users can easily copy parts of their config
heroku config -s | grep "^AWS_" | envset
# override the default path to a .env file
envset -f .env.test KEY1=value1
# a few ways to print the current .env
envset
envset print --json
# grab a single value
envset get KEY1
# keys only, thanks
envset keys
envset delete KEY1 KEY2
this cli was thrown together quickly with aider, i also put up a blog post explaining why i made this.