-
Notifications
You must be signed in to change notification settings - Fork 317
it can't run in production mode #160
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
Comments
now I have solved the problem, just add this to the config.js in the production part, production: {
url: 'http://www.xxxxxxx.com',
mail: {},
database: {
client: 'sqlite3',
connection: {
filename: path.join(process.env.GHOST_CONTENT, '/data/ghost.db')
},
debug: false
},
server: {
host: '0.0.0.0',
port: '2368'
},
// ===========add this as follow===========
paths: {
contentPath: path.join(process.env.GHOST_CONTENT, '/')
}
// ===========add this===========
} |
It looks like prior to version 1.0 the Ghost env variables weren't supported #124 #73 (comment) From this comment specifically it seems when using version 0.x you need to configure it using a custom json config |
Indeed -- I'd really recommend upgrading to Ghost 1.x ASAP, but if you can't, you'll have to deal with JSON files for configuration, unfortunately. |
@acburdine do you anticipate that there will be any more Ghost 0.x releases? Should we remove it from the supported images? What about 1.x? Is the table at https://docs.ghost.org/faq/upgrade-to-ghost-1-0/#why-upgrade-to-1-0 accurate? There don't seem to have been any releases of either 1.x or 0.x since 2.0.0. 😅 |
0.x is ok for me. in fact I don't like the default theme of both 1.x and 2.0. Json config file won't cost so much time...I use systemd to mange the ghost blog before, |
when I set "--env NODE_ENV=production", the container will crash
I use the ghost:0.11-alpine version
and here is the log
The text was updated successfully, but these errors were encountered: