Can't get a local install with `ghost install local` about ghost-cli

[acburdine]

@emolchanov Based on what you've shown, I'm not entirely sure what error is occurring, but it appears that the npm install ghost command is hanging up on one of its dependencies. I'm going to take a look later at changing from npm over to yarn, so we'll see if that helps at all.

Would you be willing/able to provide a better description of your environment so I can further help debug this?

[emolchanov]

@acburdine, sure :) What do you need?

[ecwyne]

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
npm: 3.10.10
macOS: 10.12.2
iTerm2: 3.0.13
ghost-cli: 1.0.0-alpha.8

[acburdine]

@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 ghost install local?

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.

[ecwyne]

@acburdine thanks for the rapid response!

Just updated to 1.0.0-alpha.9 and still seems to get stuck at the same place.
Downloading and installing Ghost v1.0.0-alpha.9

[acburdine]

@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]

[acburdine]

@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 ghost install local instead.

(Also, that was the original title of the issue, so if ghost install local works now then I'll close this 😉)

[ecwyne]

I actually realized that I ran ghost i without local so I started that right after I sent that picture. It's Starting ghost now. Install went MUCH faster thanks to yarn caching! 😄

[ecwyne]

Not sure how long "Starting Ghost" should take, but it's looked like this for maybe 5 mins.

[ecwyne]

After leaving this running for 30 minutes it still was saying "Starting Ghost"

I then

1. Stopped the process
2. Ran ghost config
3. Ran ghost run

[acburdine]

@ecwyne try running ghost run -D ghost install local uses the development NODE_ENV, so if you want to use the config created for a local setup you have to run Ghost in development as well.

[ecwyne]

I WAS able to start the server when I ran ghost run -D though I still get lots of Error: Cannot find module './build/Release/DTraceProviderBindings' errors

I cleared the directory and started over again one more time, got stuck at Starting Ghost but then checked if localhost:2368 was working and it WAS.

[acburdine]

Hmm...ok - would you be willing to hop on the ghost slack channel here? https://slack.ghost.org
We can chat in real time there.

Ping me once you're on (username: austin) and we can hopefully get this resolved quicker :)

[acburdine]

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

[acburdine]

@emolchanov @ecwyne Released this fix with Ghost-CLI 1.0.0-alpha.11 - please let me know if you have further issues 😄

[emolchanov]

@acburdine with Ghost-CLI 1.0.0-alpha.11 all is ok 👍 thx

[emolchanov]

@acburdine but after install, if I stop ghost with ghost stop and try to start it again with ghost start I have an error on macOs Sierra.

[acburdine]

@emolchanov So if you installed with ghost install local - you'll need to start it with ghost start -D, because ghost start by default tries to start Ghost in the production environment.

I'll do some messaging improvements this week too to try and improve the UI around this, but as a workaround ghost start -D will work 😄

[emolchanov]

@acburdine ok, thanks.