Configure a Heroku environment from a file
If you have run several apps from the same codebase (production, beta, dev, funsies, etc.), it can get cumbersome to manage the various environment variables. Now you can use the same .env files you'd use for local development configurations, complete with comments, and configure your remote Heroku apps.
By default, the tool gets the app name from the environment file name. So you can use awesomesauce-beta.env to configure awesomesauce-beta.herokuapp.com.
Install with npm install hero-envy -g.
The basic form takes an environment file to read:
$ heroenvy my-app-dev.env
You can override the app name:
$ heroenvy be-careful-with-production.env --app my-app-production
You can specify an account:
$ heroenvy my-app-dev.env --account personal
DATABASE="my_dev_db"
NAME="My Full Name" # Comments are OK
# The line below will get ignored
#LOGGING=QUIET
FAQs
Configure a Heroku environment from a file
The npm package hero-envy receives a total of 0 weekly downloads. As such, hero-envy popularity was classified as not popular.
We found that hero-envy demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
Security News
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.