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
At the moment, Ghost-CLI process management is a bit hands-off in its approach. Essentially, Ghost-CLI intends to start the ghost process (be it through a detached child process, pm2 process manager, systemd, forever, etc) and then exit, leaving only the one running Ghost process.
However, there are several features needed to make the CLI work well (#61 and #65 are the current open ones), and the current method of starting Ghost does not effectively support them. Better put, to effectively support these features, there would have to be an incredibly strict control over the process manager, making it difficult for third-party process managers (using things like upstart or pm2 or forever) to run Ghost whilst providing the information the CLI needs to run correctly.
A New Approach
The new approach that should solve most of these issues is to tightly integrate the Ghost process with a CLI command. This proposed CLI command (working name: ghost run) would run the Ghost server in a forked child process, and any process manager would start ghost run instead of starting Ghost itself.
The text was updated successfully, but these errors were encountered:
Current Approach
At the moment, Ghost-CLI process management is a bit hands-off in its approach. Essentially, Ghost-CLI intends to start the ghost process (be it through a detached child process, pm2 process manager, systemd, forever, etc) and then exit, leaving only the one running Ghost process.
However, there are several features needed to make the CLI work well (#61 and #65 are the current open ones), and the current method of starting Ghost does not effectively support them. Better put, to effectively support these features, there would have to be an incredibly strict control over the process manager, making it difficult for third-party process managers (using things like upstart or pm2 or forever) to run Ghost whilst providing the information the CLI needs to run correctly.
A New Approach
The new approach that should solve most of these issues is to tightly integrate the Ghost process with a CLI command. This proposed CLI command (working name:
ghost run
) would run the Ghost server in a forked child process, and any process manager would startghost run
instead of starting Ghost itself.The text was updated successfully, but these errors were encountered: