-
Notifications
You must be signed in to change notification settings - Fork 38
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
build(dockerfiles): split dockerfile into production and dev #1325
Conversation
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.
Thanks for tackling this! Have you tried deploying to the staging environment? I think the rename to Dockerfile.production might break the Travis pipeline / Elastic Beanstalk deployment.
I'm working on the build pipeline for edu right now, so i'll take a look at that too. Thanks for the heads up! |
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.
rebase changes on top of develop. in addition, consider using Dockerfile
and Dockerfile.dev
for deployments and localhost builds respectively
eab9aee
to
4e78116
Compare
- Removed the unused BUILD_MODE argument re #178
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
review comments taken into account in subsequent commits
Problem
The existing Dockerfile caters to both development and production builds, which increases the container startup time for developers and overall complexity.
Closes #178
Solution