Allow setting RAILS_ENV (default 'production') when deploying #87
Labels
dev 💻
Relating to development
Comments
This was referenced Dec 3, 2024
afred
added a commit
that referenced
this issue
Dec 3, 2024
Also, * Removes logs from revision. * Requires capistrano git plugin and install it, per advice of deprecation notice. * Add usage comment for `bundle exec cap aws revision` for fetching currently deployed revision. Closes #87.
foglabs
pushed a commit
that referenced
this issue
Dec 5, 2024
Sets :branch capistrano var to value of BRANCH env var Also, * Removes logs from revision. * Requires capistrano git plugin and install it, per advice of deprecation notice. * Add usage comment for `bundle exec cap aws revision` for fetching currently deployed revision. Closes #87.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Because
Introducing a new environment "demo" to AAPB requires us to be able to set the RAILS_ENV environment variable when deployinng. Currently is hard coded to "production", and that should still be the default.
Done when
Setting
RAILS_ENV=demofrom the host machine running the deployment will set the same env var and value on the remote host to which we are deploying.Is a dependency of
AAPB #2883
The text was updated successfully, but these errors were encountered: