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 notice that when even thou the documentation states that the default is backend is set to :remote,
it does not explicitly do so and this causes all commands before the run(:local) to run in :local which is
the wrong environment.
Probably due to run(:local) setting the @backend to :local
eg.
in deploy.rb
task :setup do
invoke :'nginx:setup'
run(:local) do
invoke :'setup_rails_env'
end
end
will cause nginx:setup to run in :local
task :setup do
run(:remote) do
invoke :'nginx:setup'
end
run(:local) do
invoke :'setup_rails_env'
end
end
will make sure nginx:setup is is run in :remote
task :setup do
run(:remote) do
# something else
end
invoke :'nginx:setup'
run(:local) do
invoke :'setup_rails_env'
end
end
that something else will run in :remote while nginx:setup runs in local
The text was updated successfully, but these errors were encountered:
nineten
changed the title
mina sets every command before to :local when if :remote was not explicitly
mina sets every command run(:local) to :local when if run(:remote) was not explicitly called
Mar 7, 2018
I notice that when even thou the documentation states that the default is backend is set to
:remote
,it does not explicitly do so and this causes all commands before the
run(:local)
to run in:local
which isthe wrong environment.
Probably due to
run(:local)
setting the@backend
to:local
eg.
in deploy.rb
will cause nginx:setup to run in :local
will make sure nginx:setup is is run in :remote
that
something else
will run in:remote
whilenginx:setup
runs in localThe text was updated successfully, but these errors were encountered: