Closed criadoperez closed 1 year ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed. Please reopen if needed.
If you are running the script with a any flag (lets use proxy flag an an example) and restart the service with:
./manage.sh -n testnet -a restart -f proxy
everything is restarted as expected.If you however, restart with:
./manage.sh -n testnet -a restart
the proxy container is stopped and never activated again as you can see here:Is this behavior expected? I would expect a restart to leave everything as it was. That means re-starting every container it stops.
Similar problem occurs if you are NOT running the proxy service but restart it with the proxyflag. It starts a process that wasn't running in the first place.
I would propose the following behavior instead:
./manage.sh -n testnet -a restart
doesn't accept any flags and restarts all running services.The same way the
./manage.sh -n testnet -a pull
and./manage.sh -n testnet -a down
, they pull or stop all running services.Also, if all services are down, the current behavior is that it starts them. This is less of an issue, but I would consider instead a message explaining that all services are down and you can
start
them with another command.