Running Ghost in development environment with forever in order to watch for changes and restart #24
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 5 commits
January 20, 2015 11:28
- Faster start: chown ghost sources in docker layer - Create /ghost-override volume directory in layer - Remove unused cd (WORKDIR is already /ghost)
…start ghost - installs forever in same ghost layer - start.bash runs ghost using forever when NODE_ENV=development
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Better
ghost-startscript.Now when NODE_ENV=development, ghost start using forever and its watch option in order to auto restart after code changes.
When NODE_ENV=production, ghost starts with npm start