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.
Heroku and possibly some other easy-to-host services expect
package.json
to be in the root folder. Additionally, Heroku expects the app to listen on the port it provides inPORT
environment variable.This pull request includes:
package.json
file in the root withstart
and other scripts calling the corresponding scripts from the actualpackage.json
.coffee
files before starting the appprocess.env.PORT
if possibleAt first I considered moving actually used
package.json
file fromserver
to the root, but I wasn't sure if there were some important reasons to not have it in the root. It required to update file paths in at least one file, where some node modules were linked as static files on the frontend, as thenode_modules
folder would be in the root. In the end I thought it will be safer for now to just add a new file instead of using exising one.