Specify config filename #2
Conversation
…app name with .env extension
|
+1, was looking for this feature myself |
|
+1 could really do with this for managing multiple .env files (e.g. .env for dev and .env_production for production) |
|
Updated to use heroku-api |
Small correction to README
* This eliminates the various 'DEPRECATED' notices caused by using the Heroku::Client with recent versions of the Heroku gem * Fixes issue ddollar#3
Upgrade to use the Heroku API
Correct description for overwrite example
|
👍 |
| require "heroku/command/config" | ||
|
|
||
| class Heroku::Command::Config | ||
| class Heroku::Command::Config < Heroku::Command::Base | ||
|
|
||
| # config:pull | ||
| # |
There was a problem hiding this comment.
You might want to update the comments here with the new --filename option
|
Just a heads up: when using this branch, config:pull --filename doesn't seem to overwrite an existing file. To get a new config I had to remove the file manually and then re-run it. I didn't check the file itself (probably should have), but I assumed it either didn't write to the file because it existed or appended to it. |
|
Submitted a pull request which adds a very simple --env arg which lets you specify env filename for pushing and pulling and mirrors foreman's arg for nice symmetry. |
|
Would be great to have handling similar to Foreman and Dotenv (which it uses) So that if a production-specific env file exists; |
Specify the filename to save environment variables to with the --filename option.