You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
andstaging.rb
. The variable is used to generate theProcfile
, example: https://github.com/twingly/zambezi/blob/1eb92bebd863eee12c542c9c698624759188b588/config/deploy.rb#L9-L20You 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 theproduction
branch, the production settings will be used. And vice versa.This was first reported in #5
The text was updated successfully, but these errors were encountered: