Skip to content
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

Closed
emolchanov opened this issue Dec 5, 2016 · 20 comments
Closed

Can't get a local install with ghost install local #104

emolchanov opened this issue Dec 5, 2016 · 20 comments
Labels

Comments

@emolchanov
Copy link

I get no errors, but process is active very long time without error logs and crashes.

ghost install local 2016-12-05 20-12-28
htop 2016-12-05 20-13-30

@acburdine
Copy link
Member

@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
Copy link
Author

emolchanov commented Dec 9, 2016

@acburdine, sure :) What do you need?

@acburdine acburdine added this to the 1.0.0-alpha.10 milestone Jan 4, 2017
@ecwyne
Copy link

ecwyne commented Jan 16, 2017

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
Copy link
Member

@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
Copy link

ecwyne commented Jan 16, 2017

@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
Copy link
Member

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

@acburdine acburdine modified the milestones: 1.0.0-alpha.10, 1.0.0-alpha.11 Jan 28, 2017
@ecwyne
Copy link

ecwyne commented Jan 28, 2017

screen shot 2017-01-28 at 1 45 19 pm

@acburdine
Copy link
Member

@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
Copy link

ecwyne commented Jan 28, 2017

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
Copy link

ecwyne commented Jan 28, 2017

Not sure how long "Starting Ghost" should take, but it's looked like this for maybe 5 mins.
screen shot 2017-01-28 at 1 53 27 pm

@ecwyne
Copy link

ecwyne commented Jan 28, 2017

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

screen shot 2017-01-28 at 2 40 03 pm

@acburdine
Copy link
Member

@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
Copy link

ecwyne commented Jan 28, 2017

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
Copy link
Member

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 added a commit that referenced this issue Jan 30, 2017
refs #104
- ensure usages of `assign` don’t overwrite existing objects
@acburdine acburdine added the bug label Jan 30, 2017
@acburdine
Copy link
Member

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 added a commit that referenced this issue Jan 30, 2017
closes #104
- ensure usages of `assign` don’t overwrite existing objects
@acburdine
Copy link
Member

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

@emolchanov
Copy link
Author

emolchanov commented Feb 13, 2017

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

@emolchanov
Copy link
Author

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

image

@acburdine
Copy link
Member

@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
Copy link
Author

@acburdine ok, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants