You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the way Ghost-CLI determines whether an instance of ghost is currently running is by looking at the running value in the .ghost-cli json. It works for the most part, however this can be unreliable if the system running Ghost has to restart and Ghost doesn't get a chance to shut down correctly.
Two things should probably happen:
Addition of a isRunning method to the Process Manager base class, used to check if the instance is still running
Update the logic of ghost start/ghost stop/ghost ls to call that particular process manager method if the running property is set in the cli config file, and if the process manager returns false, unset the property from the CLI.
The text was updated successfully, but these errors were encountered:
closesTryGhost#207
- updates the running check to make sure the process is actually running
- adds a method to the process manager class (required to implement)
closes#207
- updates the running check to make sure the process is actually running
- adds a method to the process manager class (required to implement)
Currently the way Ghost-CLI determines whether an instance of ghost is currently running is by looking at the
running
value in the.ghost-cli
json. It works for the most part, however this can be unreliable if the system running Ghost has to restart and Ghost doesn't get a chance to shut down correctly.Two things should probably happen:
isRunning
method to the Process Manager base class, used to check if the instance is still runningghost start
/ghost stop
/ghost ls
to call that particular process manager method if therunning
property is set in the cli config file, and if the process manager returns false, unset the property from the CLI.The text was updated successfully, but these errors were encountered: