-
Notifications
You must be signed in to change notification settings - Fork 1
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
Provide production ready Dockerfile #245
base: development
Are you sure you want to change the base?
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.
There are a couple of small things here but overall my main concern is how this Dockerfile is intended to interact with a database (see my comment on the entrypoint line).
RUN pip install --no-cache-dir -r requirements.txt | ||
|
||
EXPOSE ${APPLICATION_PORT} | ||
ENTRYPOINT ["/var/www/request-broker/entrypoint.sh", "apache"] |
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.
The issue with using the existing entrypoint.sh is that the wait-for-it.sh
check for database status has a hardcoded host and port. This raises the question of whether this Dockerfile is intended to be used in conjunction with a compose file. If so, it may make sense to provide a prod compose file in addition to this Dockerfile.
Resolves #241 with a
Dockerfile.prod
which uses an Apache WSGI configuration.