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
I am looking to deploy two instances of a Rails app on a VPS - one for production and one for sandbox (or staging / testing).
But it seems to me that mina wouldn't allow it.
In task rails:db_migrate, rails_env is hard-coded to production with no means to override it. And this rails_env then percolates down to bundle_prefix and thence to rake and rails etc.
Could a way be provided therefore to set :rails_env to something other than the default production?
The text was updated successfully, but these errors were encountered:
I realized after I filed the issue that set :rails_env, 'staging' would work. I wrongly assumed that once set a value could not be changed - not realizing that if set is passed a block, then that block will be used by fetch to return the updated value.
I am looking to deploy two instances of a Rails app on a VPS - one for production and one for sandbox (or staging / testing).
But it seems to me that
mina
wouldn't allow it.In task
rails:db_migrate
,rails_env
is hard-coded toproduction
with no means to override it. And thisrails_env
then percolates down tobundle_prefix
and thence torake
andrails
etc.Could a way be provided therefore to
set :rails_env
to something other than the defaultproduction
?The text was updated successfully, but these errors were encountered: