-
Notifications
You must be signed in to change notification settings - Fork 4
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
AWS Paas Migration Changes #1264
Conversation
package.json
Outdated
@@ -44,6 +44,7 @@ | |||
"clean": "rm -f ./run/static/webpack_bundles/*", | |||
"heroku-prebuild": "", | |||
"heroku-postbuild": "npm run build", | |||
"start": "echo starting", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is start
a placeholder for a future script? (We've tended not to introduce placeholders into production code.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again this is a work-around for node.js buildpack
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed with @emileswarts to replace "echo starting"
with something that documents the dummy "start"
script entry - e.g. "start": "dummy entry for node.js buildpack workaround"
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pointing this at bash web-worker-entrypoint.sh
will be sufficient for this workaround, but means that we can't add the comment to indicate that it's a workaround.
7f0a9ae
to
07586b2
Compare
07586b2
to
19f1376
Compare
d30c74f
to
805ca50
Compare
805ca50
to
ed2ffaa
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Changes to enable AWS migration
Why
To facilitate the application(s) in the repo to be deployed on to the new AWS platform