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

Ghost Cli throw error Config file is not valid JSON #436

Closed
1 task done
ittus opened this issue Aug 11, 2017 · 3 comments · Fixed by #438
Closed
1 task done

Ghost Cli throw error Config file is not valid JSON #436

ittus opened this issue Aug 11, 2017 · 3 comments · Fixed by #438
Assignees
Labels

Comments

@ittus
Copy link

ittus commented Aug 11, 2017

This issue is a

  • Bug Report

Summary

Ghost doctor throw Config file is not valid JSON, while config.production.json is valid

{
	"url": "http://*****.com",
	"server": {
		"port": 2368,
		"host": "127.0.0.1"
	},
	"database": {
		"client": "mysql",
		"connection": {
			"host": "localhost",
			"user": "ghost-657",
			"password": "prodpassword",
			"database": "proddatabase"
		}
	},
	"mail": {
		"transport": "SMTP",
		"options": {
			"service": "Mailgun",
			"auth": {
				"user": "[email protected]",
				"pass": "5ca2eff1231ee123fe2f96333199502b3aa96ac"
			}
		}
	},
	"logging": {
		"transports": [
			"file",
			"stdout"
		]
	},
	"process": "systemd",
	"paths": {
		"contentPath": "/var/www/ghost/content"
	}
}

Steps to Reproduce (for a bug report)

  1. Install ghost 1.5.2 in /var/www/ghost
  2. Run ghost in production mode
  3. Run ghost doctor startup
  4. Receive error:
✖ Validating config
A ConfigError occurred.

Error detected in the undefined configuration.

Message: Config file is not valid JSON

Debug Information:
    Node Version: v6.11.2
    Ghost-CLI Version: 1.0.3
    Environment: production
    Command: 'ghost doctor startup'

Technical details (will be automatically output by Ghost-CLI if an error occurs):

  • OS: Ubuntu 16.04
  • Node Version: 6.11.2
  • Ghost-CLI Version: 1.0.3
  • Environment: production
  • Command: ghost doctor startup
@acburdine
Copy link
Member

@ittus does this occur on ghost start, or just when you run ghost doctor startup?

@acburdine
Copy link
Member

Can confirm.

@acburdine acburdine self-assigned this Aug 11, 2017
@acburdine acburdine added the bug label Aug 11, 2017
acburdine added a commit to acburdine/Ghost-CLI that referenced this issue Aug 11, 2017
closes TryGhost#436
- if environment is not passed in startup context,
run checkValidInstall and checkEnvironment to ensure we run this correctly
acburdine added a commit to acburdine/Ghost-CLI that referenced this issue Aug 11, 2017
closes TryGhost#436
- if environment is not passed in startup context,
run checkValidInstall and checkEnvironment to ensure we run this correctly
- add tests for startup checks
acburdine added a commit that referenced this issue Aug 11, 2017
closes #436
- if environment is not passed in startup context,
run checkValidInstall and checkEnvironment to ensure we run this correctly
- add tests for startup checks
@ittus
Copy link
Author

ittus commented Aug 12, 2017

Just ghost doctor startup, ghost start works fine

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

Successfully merging a pull request may close this issue.

2 participants