-
-
Notifications
You must be signed in to change notification settings - Fork 229
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
You are able to skip systemd, but you are actually not #308
Labels
Comments
vikaspotluri123
added a commit
to vikaspotluri123/Ghost-CLI
that referenced
this issue
Oct 7, 2020
vikaspotluri123
added a commit
to vikaspotluri123/Ghost-CLI
that referenced
this issue
Oct 9, 2020
vikaspotluri123
added a commit
to vikaspotluri123/Ghost-CLI
that referenced
this issue
Oct 9, 2020
vikaspotluri123
added a commit
to vikaspotluri123/Ghost-CLI
that referenced
this issue
Oct 9, 2020
vikaspotluri123
added a commit
to vikaspotluri123/Ghost-CLI
that referenced
this issue
Oct 10, 2020
vikaspotluri123
added a commit
to vikaspotluri123/Ghost-CLI
that referenced
this issue
Oct 10, 2020
acburdine
pushed a commit
that referenced
this issue
Oct 10, 2020
This should be fixed w/ #1311 - process manager is reverted to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you run
ghost install
and you skip systemd setup, you won't be able to start Ghost, as linux & systemd setup is required, because you will run into[you have to use
--process local
explicit if want to use the local process manager].Should we remove the prompt for systemd? Or change the prompt to e.g. "Are you ready to setup systemd?". Or any other ideas?
I am still confused about this step. Both @AileenCGN and @cobbspur find that confusing as well.
It was also mentioned, that people might not even know what systemd means.
The text was updated successfully, but these errors were encountered: