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

Procfile settings not read from mapped git branch #10

Open
jage opened this issue Mar 4, 2014 · 0 comments
Open

Procfile settings not read from mapped git branch #10

jage opened this issue Mar 4, 2014 · 0 comments

Comments

@jage
Copy link
Contributor

jage commented Mar 4, 2014

Procfile is generated client side, uses settings from file-system instead of git branch

In Zambezi we have the ability to tweak the number of processes by setting a capistrano variable in production.rb and staging.rb. The variable is used to generate the Procfile, example: https://github.com/twingly/zambezi/blob/1eb92bebd863eee12c542c9c698624759188b588/config/deploy.rb#L9-L20

You can get some surprises by this though.

Since this is done client side, it does not use the settings checked in to the specific stage branch, instead it reads from the filesystem. If you run cap staging deploy when you're in the production branch, the production settings will be used. And vice versa.

This was first reported in #5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant