-
Notifications
You must be signed in to change notification settings - Fork 3
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
Feat: production container #123
Conversation
a713765
to
a456940
Compare
97ef3c4
to
4facc22
Compare
a456940
to
5d37d95
Compare
4facc22
to
a192078
Compare
5d37d95
to
8483950
Compare
8483950
to
4b76dbc
Compare
547792a
to
00082f6
Compare
nginx listens on this port
00082f6
to
f610a12
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.
Rebuilt container and ran successfully
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.
I was also able to rebuild and reopen the devcontainer, and I could run the server
container with docker compose
.
Created cal-itp/docker-python-web#2 as a part of reviewing this
Closes #111
This PR changes the base image to use our new
cal-itp/docker-python-web
image hosted on GitHub Container Registry.This base image bakes in
nginx
andgunicorn
- andbin/start.sh
runs the app through those services.Developers shouldn't notice a difference running the app locally - either inside the devcontainer in debug mode, or by running the container with
docker compose
.