Closed alper closed 3 years ago
Perhaps I'm misunderstanding the question, but honcho start
runs a foreground process, so the idea of a honcho stop
command doesn't make a great deal of sense to me.
Yeah, I get that but say we use the honcho
command in our testing sequence to start everything before doing functional tests, we would like to tear everything down again.
I get that we could start things manually maybe but honcho is a compact and DRY way to start everything that needs to be started.
@alper One option is to run your tests with honco
as well:
# Procfile.e2e
app: python manage.py runserver
test: pytest e2e_tests
via honcho --procfile Procfile.e2e
. I have an example of this pattern here.
Ah, thanks. That's quite clever!
Closing this as I don't believe there are any changes in Honcho needed here.
We have a rather hacky Makefile where I'm looking to replace a bunch of stuff with
honcho start
but I'm not finding an equivalent stop command.The thing is we have some functional tests for which the python stuff needs to run and when those tests have been done it needs to be stopped again. Any way to address this using honcho?
The current approach stores a PID and then kills that I believe.