-
-
Notifications
You must be signed in to change notification settings - Fork 220
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
Can't get a local install with ghost install local
#104
Comments
@emolchanov Based on what you've shown, I'm not entirely sure what error is occurring, but it appears that the Would you be willing/able to provide a better description of your environment so I can further help debug this? |
@acburdine, sure :) What do you need? |
I am having the exact same issue. Literally left it running overnight to no avail. Happy to help in any way I can node: v6.9.4 |
@ecwyne sorry you're having trouble as well! Can both of you update to 1.0.0-alpha.9 (of the CLI, just published it) and see if that solves the issue with If that doesn't fix the issue, I'm planning on refactoring the CLI tool to use Yarn here soon, so it should make it a little more stable wrt the installation process. |
@acburdine thanks for the rapid response! Just updated to 1.0.0-alpha.9 and still seems to get stuck at the same place. |
@emolchanov @ecwyne I just released a new version of the CLI (1.0.0-alpha.10) - can you try that and let me know if the issue is fixed? The new version uses Yarn rather than npm - so you'll need to install Yarn first 😄 Fortunately though - it should improve reliability of things tremendously. |
@ecwyne so - the issue there is that Ghost by default tries to run on a system stack that is Ubuntu 16, nginx, and systemd-based. The problem you're getting is because you're trying to run this on a mac. In the next version, there will be more strides given to ensure that ^ error doesn't occur, and the process manager falls back to the local one, but for the moment just run (Also, that was the original title of the issue, so if |
I actually realized that I ran |
@ecwyne try running |
I WAS able to start the server when I ran I cleared the directory and started over again one more time, got stuck at |
Hmm...ok - would you be willing to hop on the ghost slack channel here? https://slack.ghost.org Ping me once you're on (username: austin) and we can hopefully get this resolved quicker :) |
refs #104 - ensure usages of `assign` don’t overwrite existing objects
I'm actually fairly certain that the bug that caused this issue initially is the same bug that caused the second issue - this should be fixed in #139 |
closes #104 - ensure usages of `assign` don’t overwrite existing objects
@emolchanov @ecwyne Released this fix with Ghost-CLI 1.0.0-alpha.11 - please let me know if you have further issues 😄 |
@acburdine with Ghost-CLI 1.0.0-alpha.11 all is ok 👍 thx |
@acburdine but after install, if I stop ghost with |
@emolchanov So if you installed with I'll do some messaging improvements this week too to try and improve the UI around this, but as a workaround |
@acburdine ok, thanks. |
I get no errors, but process is active very long time without error logs and crashes.
The text was updated successfully, but these errors were encountered: