You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context
Currently, our Dockerfile uses python app.py to deploy the application. This method is fine for development but not ideal for production environments, where a WSGI server is recommended for better performance and handling of concurrent requests.
Problem Statement
Running the application directly with python app.py is not suitable for production as it lacks the robustness and efficiency provided by a WSGI server. This could lead to performance issues and difficulties in handling multiple requests in a real-world scenario.
Acceptance Criteria
Replace CMD ["python", "app.py"] in the Dockerfile with a command that uses a WSGI server (e.g., gunicorn or uWSGI).
Ensure that the WSGI server is correctly configured to serve the application in production.
Update the Dockerfile to reflect this change and ensure it builds successfully.
Test the deployment to verify that the application works as expected under the new setup.
Description
Context
Currently, our Dockerfile uses
python app.py
to deploy the application. This method is fine for development but not ideal for production environments, where a WSGI server is recommended for better performance and handling of concurrent requests.Problem Statement
Running the application directly with
python app.py
is not suitable for production as it lacks the robustness and efficiency provided by a WSGI server. This could lead to performance issues and difficulties in handling multiple requests in a real-world scenario.Acceptance Criteria
CMD ["python", "app.py"]
in the Dockerfile with a command that uses a WSGI server (e.g.,gunicorn
oruWSGI
).Additional Information (Optional)
For reference, consult the Flask deployment documentation on using a WSGI server.
The text was updated successfully, but these errors were encountered: