Skip to content

Development: use gunicorn for web and proxito #9977

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

Merged
merged 1 commit into from
Feb 2, 2023

Conversation

humitos
Copy link
Member

@humitos humitos commented Feb 2, 2023

Match production environment by using gunicorn instead of the Django development server.

It uses a previous work that @agjohnson did to reload the web and proxito processes inside Docker using nodemon. It requires this "common" PR: readthedocs/common#160

  • it keeps the same functionality from manage.py runserver (auto reload --being able to turn it on/off)
  • matches environment from production
  • allows handling multiple requests in a nicer way locally
  • site works faster locally (maybe it's my impression, but 🤷🏼 )

Match production environment by using `gunicorn` instead of the Django
development server.
@humitos humitos requested a review from a team as a code owner February 2, 2023 16:00
@humitos humitos requested a review from stsewd February 2, 2023 16:00
@humitos humitos merged commit c99aa03 into main Feb 2, 2023
@humitos humitos deleted the humitos/gunicorn-development branch February 2, 2023 18:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants