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

Ignore release command? #5

Closed
theflow opened this issue Oct 20, 2017 · 2 comments
Closed

Ignore release command? #5

theflow opened this issue Oct 20, 2017 · 2 comments

Comments

@theflow
Copy link

theflow commented Oct 20, 2017

Hi,

thanks for hivemind, I really enjoy using it!

I've recently added a release command to my Procfile (see https://devcenter.heroku.com/articles/release-phase). And now hivemind stops working as it recognizes the task exit and shuts everything down.

Would it make sense to ignore release by default? That's the behavior of heroku local

Cheers,
Florian

@DarthSim
Copy link
Owner

Hi,
I don't think it will be predictable behavior if hivemind will ignore hardcoded process names. You can specify processes which you want to run with -l param. As for our team, we have two procfiles - one for production and one for development.
Have you tried overmind? With it, you can specify processes which can die after execution without stopping the rest ones.

@ivanovv
Copy link

ivanovv commented Feb 7, 2018

I +1 @theflow suggestion.

I don't think it will be predictable behavior if hivemind will ignore hardcoded process names

We can print a warning in red that release process is ignored and the workaround for that will be to use -l param.

If you are strictly against this,maybe you can add an option to ignore some processes then? Using -l to specify 3 processes (if we have 4 in Procfile) looks cumbersome to me. Something like -i / --ignore, so that the final command will be like

$> hivemind -i release

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

3 participants