Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Current" deploy directory for export #44

Open
hut8 opened this issue Mar 16, 2016 · 2 comments
Open

"Current" deploy directory for export #44

hut8 opened this issue Mar 16, 2016 · 2 comments

Comments

@hut8
Copy link

hut8 commented Mar 16, 2016

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?

@pratik60
Copy link

@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.

What did you do?

@hut8
Copy link
Author

hut8 commented Jun 29, 2016

Personally I stopped using capistrano-foreman and wrote the script myself. It works great 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants