flâneur

Deploying Django • Buttondown

buttondown.com · 2,121 words · saved by 1 readers

Over the past two years, I’ve learned a hell of a lot about deploying Django apps into production. And yes, I really do mean a HELL of a lot. While Django is a great web framework, one of its primary weaknesses (in my opinion) is a lack of strong deployment documentation and community standards. There has been no easy way (until now, kinda) to deploy your apps into production in a reliable, simple fashion. Period. Sure, there are excellent best practices that a few awesome programmers follow, but for the majority of users, the best practices are just too complex and time consuming to setup and administer for typical site. Let’s pretend, for a moment, that you’re an intermediate Django programmer. You spend 8 hours a day working on a single project that is built purely in python / Django. Your primary main objective is to keep your users happy (fix bugs, release new features, etc.). You’re fairly familiar with the Django ecosystem: you know which apps to look at for solving various prob

October 29, 2011 Deploying Django Over the past two years, I’ve learned a hell of a lot about deploying Django apps into production. And yes, I really do mean a HELL of a lot. While Django is a great web framework, one of its primary weaknesses (in my opinion) is a lack of strong deployment documentation and community standards. There has been no easy way (until now, kinda ) to deploy your apps into production in a reliable, simple fashion. Period. Sure, there are excellent best practices that a few awesome programmers follow, but for the majority of users, the best practices are just too comp

saved by

related reading