Running Rendón Burgers in production requires two changes from the default development setup: replacing the Flask development server with Gunicorn, and securing the MongoDB Atlas connection string using environment variables instead of hardcoding it in source code.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/EduCabrera-k/Menu_Hamburguesas/llms.txt
Use this file to discover all available pages before exploring further.
Running with Gunicorn
Gunicorn is the recommended WSGI server for running Flask applications in production. It is already included inrequirements.txt.
Start the server with multiple workers and bind it to all interfaces:
-w 4— Spawns four worker processes. A common starting point is(2 × CPU cores) + 1.-b 0.0.0.0:8000— Binds the server to port 8000 on all network interfaces, making it accessible from outside the host machine.
Set
debug=True to False in app.py before running in production. The Flask development server’s debug mode exposes an interactive debugger that must never be accessible in a production environment.MongoDB Atlas connection
The application connects to MongoDB Atlas using amongodb+srv:// URI. The URI format is:
rendon_burger_db. The three collections used are:
| Collection | Purpose |
|---|---|
pedidos_activos | Active orders in progress |
historial_ventas | Completed order history |
inventario_stock | Item availability flags |
MONGO_URI as a secret environment variable in the platform’s dashboard rather than in a shell script.
Views and their URLs
Once the server is running, the three application views are available at:| URL | View | Audience |
|---|---|---|
/ | Customer menu | Customers placing orders |
/cocina | Kitchen dashboard | Kitchen staff managing the order queue |
/reporte | Sales report | Management reviewing daily sales data |
app.py and do not require any additional configuration to function in production.