More UX Improvements #152
Assignees
Labels
Comments
acburdine
added a commit
to acburdine/Ghost-CLI
that referenced
this issue
Feb 15, 2017
refs TryGhost#152 - if a development config exists but not a production one, running ghost start without the `-D` option will still run in development mode - fixes issues when running `ghost start` in a local install
acburdine
added a commit
that referenced
this issue
Feb 15, 2017
refs #152 - if a development config exists but not a production one, running ghost start without the `-D` option will still run in development mode - fixes issues when running `ghost start` in a local install
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue tracks some of the necessary UX updates that need to go into Ghost-CLI before 1.0
ghost startdetection of config file.Currently,
ghost startruns in production, andghost start -Druns in development, which is the same as all of the other ghost commands. While this makes sense, it can be somewhat confusing when you install ghost viaghost install local, runghost stopand then runghost startagain. While the config validation (see #26) will makeghost startfail should the file not exist, theghost startcommand should be smart enough to detect what config files exist, and default to the existing one (be it production or development). If both a production and a development config exist,ghost startwill behave as before.More coming...
The text was updated successfully, but these errors were encountered: