Skip to content
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

Closed
aspiers opened this issue Mar 3, 2013 · 4 comments · Fixed by #70
Closed

rails_env / unicorn_env / app_env are redundant or undocumented #46

aspiers opened this issue Mar 3, 2013 · 4 comments · Fixed by #70

Comments

@aspiers
Copy link
Contributor

aspiers commented Mar 3, 2013

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 to rails_env).

@vitoravelino
Copy link

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.

@aspiers
Copy link
Contributor Author

aspiers commented Aug 19, 2013

I have investigated, and actually they are not the same. I also found a bug with app_env which had independently been reported as #64. I'm working on a fix for all this now ...

@sfsekaran
Copy link
Contributor

@aspiers Is this issue closable, then?

@aspiers
Copy link
Contributor Author

aspiers commented Aug 19, 2013

No, it's better to wait until it's resolved before closing.

aspiers pushed a commit to aspiers/capistrano-unicorn that referenced this issue Aug 20, 2013
… variables

This is the first step towards resolving sosedoff#46 and sosedoff#64.
aspiers pushed a commit to aspiers/capistrano-unicorn that referenced this issue Aug 20, 2013
aspiers pushed a commit to aspiers/capistrano-unicorn that referenced this issue Aug 20, 2013
This is the final commit in the series which fixes sosedoff#46.
aspiers pushed a commit to aspiers/capistrano-unicorn that referenced this issue Aug 22, 2013
… variables

This is the first step towards resolving sosedoff#46 and sosedoff#64.
aspiers pushed a commit to aspiers/capistrano-unicorn that referenced this issue Aug 22, 2013
aspiers pushed a commit to aspiers/capistrano-unicorn that referenced this issue Aug 22, 2013
This is the final commit in the series which fixes sosedoff#46.
aspiers pushed a commit to aspiers/capistrano-unicorn that referenced this issue Sep 2, 2013
… variables

This is the first step towards resolving sosedoff#46 and sosedoff#64.
aspiers pushed a commit to aspiers/capistrano-unicorn that referenced this issue Sep 2, 2013
aspiers pushed a commit to aspiers/capistrano-unicorn that referenced this issue Sep 2, 2013
This is the final commit in the series which fixes sosedoff#46.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants