If this gem is required, and `rails_env` is not specified, it defaults it to `production`. This breaks `cap staging XXX` silently..
Closed this issue · 3 comments
ktaragorn commented
Capistrano 3 doesnt require us to set rails_env, so I havent set it. However on requiring this gem, it auto sets that to production. Thus deploying to staging is now broken. This is handled by setting rails_env as specified in the todo.. but this should just not happen.. Silently breaking capistrano even when not explicitly using the db tasks.. is evil...
Wasted a lot of time before we spotted the dark blue RAILS_ENV=production over the black background of the terminal..
tomav commented
Yes, same problem here:
cap staging db:local:sync uses production and not staging.
I expected to get staging db into my local (development) environment.