-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rails_env
/ unicorn_env
/ app_env
are redundant or undocumented
#46
Comments
Hey @aspiers! I just saw that I can pass params through the command line and access them inside the deploy file. That would solve that problem that I had without having to change anything at all. But I agree that those 3 variables look the same. 👍 to this issue. |
I have investigated, and actually they are not the same. I also found a bug with |
@aspiers Is this issue closable, then? |
No, it's better to wait until it's resolved before closing. |
… variables This is the first step towards resolving sosedoff#46 and sosedoff#64.
This contributes towards resolving sosedoff#46 and sosedoff#64.
This is the final commit in the series which fixes sosedoff#46.
… variables This is the first step towards resolving sosedoff#46 and sosedoff#64.
This contributes towards resolving sosedoff#46 and sosedoff#64.
This is the final commit in the series which fixes sosedoff#46.
… variables This is the first step towards resolving sosedoff#46 and sosedoff#64.
This contributes towards resolving sosedoff#46 and sosedoff#64.
This is the final commit in the series which fixes sosedoff#46.
It's not at all clear why we need three variables which apparently serve the same purpose:
rails_env
unicorn_env
app_env
If they are really all necessary and serve different purposes then they should be documented properly. Otherwise they should be collapsed to just one variable, or two at most (since I can just about imagine that someone might want
unicorn_env
to have a different value torails_env
).The text was updated successfully, but these errors were encountered: