Use Gunicorn for container server

[tylerslonecki]

No description provided.

[Copilot]

🟡 Changes recommended

Gunicorn’s default bind port logic can diverge from the application’s production port defaults when APP_ENV=production and APP_PORT is unset, risking misconfigured container routing.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Adds Gunicorn as the container’s runtime server configuration so the app runs under a production-grade WSGI process manager instead of python app.py.

Changes:

• Introduces gunicorn.conf.py with worker/threading, logging, recycling, and optional TLS configuration driven by environment variables.
• Updates Dockerfile to copy the Gunicorn config and start the container with gunicorn ... app:server.

File summaries

File	Description
gunicorn.conf.py	New Gunicorn configuration for container runtime (bind/workers/logging/TLS).
Dockerfile	Switch container startup from python app.py to gunicorn using the new config.

Review details

• Files reviewed: 2/2 changed files
• Comments generated: 1
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.