Skip to content
This repository has been archived by the owner on Nov 12, 2018. It is now read-only.

Ghost is looking in node_modules for the content directory. #1

Closed
jondavidjohn opened this issue Feb 20, 2014 · 3 comments
Closed

Ghost is looking in node_modules for the content directory. #1

jondavidjohn opened this issue Feb 20, 2014 · 3 comments

Comments

@jondavidjohn
Copy link

I'm trying to mimic your setup here and I keep hitting this error when trying to start it up

ERROR: ENOENT, readdir '/Users/jon/Sites/site.dev/node_modules/ghost/content/themes'

Which tells me it's not picking up the content directory at the root, any thoughts that might be helpful in getting this type of setup working? Any special config.js options needed for this type of setup?

@jondavidjohn
Copy link
Author

I've figured out I need a later version than 0.4.1 to do this, so it's now working, but it looks to still be using the content directory inside node_modules/ghost/content... Is there a special configuration directive to get it to look at the content directory at the site root?

@jondavidjohn
Copy link
Author

Don't mind me, just talking myself through it 😄

Figured it out, there is a path.contentPath config option now in the config.sample.js that I missed after updating my ghost install.

👍

Good to go now.

@hswolff
Copy link
Owner

hswolff commented Feb 23, 2014

Excellent sleuthing! For future reference I created this wiki page with all NPM related info: https://github.com/TryGhost/Ghost/wiki/Using-Ghost-as-a-NPM-module

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

No branches or pull requests

2 participants