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

Why honcho in particular? #11

Closed
GildedHonour opened this issue Mar 15, 2021 · 1 comment
Closed

Why honcho in particular? #11

GildedHonour opened this issue Mar 15, 2021 · 1 comment
Labels
question Further information is requested

Comments

@GildedHonour
Copy link

GildedHonour commented Mar 15, 2021

  1. Why is honcho in particular used here?

  2. What's the neccessity? Why not run all of them without honcho, as ordinary processes? Is it specific to the fact that it's all done in Docker?

@joydark joydark added the question Further information is requested label Mar 16, 2021
@DezzK
Copy link
Contributor

DezzK commented Mar 16, 2021

  1. Honcho allows orchestrating several processes in parallel using a single and simple configuration file (procfile).
  2. It's not specific to Docker. Of course, you don't have to use honcho and similar tools, but, in that case, you have to orchestrate all processes manually. For example, if one of the processes failed to start, you have to stop all other processes. Honcho can simplify this as much, as possible.

@DezzK DezzK closed this as completed Mar 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants