Production deployment configuration for azblog
By RepoJournal , from @anurag629's public GitHub activity
Backfilled
Anurag Verma pushed 19 commits across 8 pull requests to anurag629/azblog, preparing the Django application for production deployment with WSGI configuration and allowed hosts.
The work centered on configuring the azblog Django application for production use. Verma created a production.py file [1] and modified the WSGI configuration [2] to support production serving. Allowed hosts were added to the Django settings, first as a general configuration [6] and then specifically set to egblog.me [9].
Parallel to the production setup, Verma made several updates to the collagepaper feature, adding district year display functionality across multiple commits [3] and merging those changes through pull requests [4]. The district year display feature appeared in multiple iterations [5], [7], suggesting refinement of that feature over the course of the day.
The day concluded with multiple rounds of production-related changes [8], [10], bundled into the final pull request [11] that completed the deployment configuration work.
One email a day. Unsubscribe in one click.
A short briefing every day anurag629 ships something — in about 3 minutes.
One email a day. Unsubscribe in one click. Read a past issue →
References
- [1] created produvtion.py file anurag629/azblog
- [2] changes wsgi file for production anurag629/azblog
- [3] district year display anurag629/azblog
- [4] Merge pull request #9 from anurag629/collagepaper anurag629/azblog
- [5] district year display anurag629/azblog
- [6] addedallowed host anurag629/azblog
- [7] district year display anurag629/azblog
- [8] changes for production anurag629/azblog
- [9] allowed host to egblog.me anurag629/azblog
- [10] changes for production anurag629/azblog
- [11] changes for production ↗ anurag629/azblog