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
Hey. I'm using this script to deploy an application that uses sidekiq onto Ubuntu 14.04 (so that means by default I get Upstart, for better or for worse 😉). Upon invoking foreman:export, I end up with an upstart script that ends in:
exec su - rails-assets -c 'cd /home/my-app-user/rails-apps/my-app/releases/20160311190512; # ...
On the README, in the USAGE section, it seems like you're suggesting that exporting the Procfile like this is a one time deal and need not be done on every deployment. Is that right? I did this, and of course it worked and I didn't actually examine the Upstart script which was generated. But then after 5 deploys, my sidekiq stopped existing 💥 ❗
Personally, at the least, I think this should have clearer documentation (which of course I will be happy to add). But also, do you think that maybe by default having it export the current (symlinked) path would be more intuitive?
The text was updated successfully, but these errors were encountered:
@hut8 Noticed the same thing on examining the file. Current symlink will be far better in our use case. Other things I noticed, that it doesn't automatically restart on ever deployment, for me it didn't even try to start altogether, which makes me question whether I'm doing things wrong.
Hey. I'm using this script to deploy an application that uses sidekiq onto Ubuntu 14.04 (so that means by default I get Upstart, for better or for worse 😉). Upon invoking
foreman:export
, I end up with an upstart script that ends in:On the README, in the USAGE section, it seems like you're suggesting that exporting the Procfile like this is a one time deal and need not be done on every deployment. Is that right? I did this, and of course it worked and I didn't actually examine the Upstart script which was generated. But then after 5 deploys, my sidekiq stopped existing 💥 ❗
Personally, at the least, I think this should have clearer documentation (which of course I will be happy to add). But also, do you think that maybe by default having it export the
current
(symlinked) path would be more intuitive?The text was updated successfully, but these errors were encountered: