|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Ai||863||4 years ago||6||mit||C++|
|Repo for work for AI Survey|
|Orientation||368||2 years ago||56||mit||Ruby|
|Your best weapon in the fight against outdated documentation.|
|Envied||327||3 years ago||9||mit||Ruby|
|Ensures presence and type of your app's ENV-variables (mirror)|
|Gistblog||297||9 years ago||mit||CSS|
|A blogging platform built on Github gists|
|[Utility] Push and pull heroku environment variables to your local env|
|Wordpress 12factor||204||6 years ago||8||PHP|
|WordPress, the Twelve-Factor way: fully managed using Composer and configured using environment variables.|
|Heroku.json||166||9 years ago||mit||Ruby|
|Setting up Heroku apps made easy.|
|Api V2||109||6 years ago||apache-2.0||Elixir|
|Flask Appconfig||80||164||1||6 years ago||17||December 15, 2021||4||mit||Python|
|Configures Flask applications in a canonical way. Also auto-configures Heroku. Aims to standardize configuration.|
|You favorite book library|
Push and pull your Heroku configs to your local environment.
Heavily inspired by ddollar's version, but using the new Heroku cli.
Running this code has the potential to delete your configurations if misused.
-o flag will overwrite values at the destination. Only use that if the source has more up to date info and you're feeling brave. Otherwise, this merges configs and is fairly safe. Just thought you should know.
-c flag will delete values that didn't exist locally when you pushed. Only use it if you know that.
You can install the package by running
% heroku plugins:install heroku-config
This package includes two commands:
heroku config:pull: Writes the contents of
heroku configinto a local file
heroku config:push: Writes the contents of a local file into
As of version 1.6.0, the
heroku-config supports modifying pipeline config variables with the
heroku help config:pull and
heroku help config:push to see a full list of flags.
There's a lot of flexibility when it comes to how you can format your file. Key capitalization can go either way and there can be spacing around the
= on one, both, or neither side. There can also be a leading
export if you want to use the same file to populate your local environment. Since Heroku runs on linux, variable names must conform to those valid in unix. If you want to use unsupported characters in your var names, run commands with the
-e flag. There's also support both unix and windows-style newlines (though only one type per file).
Multiline variables are fine as long as they're surrounded by
All of the following are valid lines:
#comment NODE_ENV= test source =local job = programming DB_STRING=mongo://[email protected]:4567 export THING=3 multiline="this can have as many lines # comments are still ignored as it wants"
The following are all invalid lines:
# comment with leading space bad_key=nono key with-dash=andspace multiline='bad because it uses single quotes'
You'll need Node version
>= 6.0. If you want to match exactly, check out the heroku cli's node version here. I like nvm for managing multiple node versions.
After cloning, follow these instructions to run locally! I welcome pull requests with fixes or new features.