How is this possible?
I am currently using the Capistrano recipe
is that what I have:
# delay for "delayed job recipes" / Dishes "set is required: rails_env," production "#" deployment: stop "," delayed_gub: "deployment: restart", "delayed_gub: restart" After I can not understand the "very good" capiterno phases, the solution may be to set the right action in the right step. Update Every time I deploy I am executing
'delay_yjob: restart' Is it Is it really necessary? Is there any way to start the delay_job again when needed? Or is it always needed?
I'm also not sure what you want but probably simple
less payable when when: stop what will happen from the command line ?
cap -T UPD ATE . Whenever you deploy, this is a best practice to restart your late-working workers. In the end, workers execute your code, and who change between the deployment. Now, if your workers change at least the changes (which include Rail Boot process, environment files, analyzer, settings, models, which you use, etc.), and you want to take care of yourself, then Just delete the hook such as
deploy.rb after "deployment: stop", "delayed_ when: pause" and you are okay: DJ work will still be at your disposal, but do not trigger them during the deployment Will be done.
No comments:
Post a Comment