DevOps for Django - The Best Deployment Strategy
Join the DZone community and get the full member experience.
Join For FreeDeploying Django is hard according to blogger Randall Degges. His initial post about Django deployment got a lot of attention from some big time developers in the Django community. What he decided to do as a result was to start documenting the best deployment strategies around for Django and post them. Right now he's just outlined what he wants to do, which he will follow up with his company's specific use case for Django and pain points:
Degges admits that a lot of the problem isn't centered on Django but the fact that he's working with so many technologies, services, and libraries to make a Django stack do what he wants. Such is life in open source land.
Source: http://rdegges.com/devops-django-part-1-goals
In an perfect world, as a developer, I should be able to:
Furthermore, I want my application and all of its related infrastructure components to *just work*, and require NO maintenance. --Randall Degges
- Run a single command to deploy my application into production.
- Run a single command to automatically scale up (or scale down) my application.
- Instantly add services to my infrastructure that my application needs (memcached, redis,postgresql, etc.).
- Have full access to logs and metrics for all parts of my infrastructure, so that I can find problems and fix them based on facts, not assumptions.
Degges admits that a lot of the problem isn't centered on Django but the fact that he's working with so many technologies, services, and libraries to make a Django stack do what he wants. Such is life in open source land.
Source: http://rdegges.com/devops-django-part-1-goals
Django (web framework)
DevOps
Opinions expressed by DZone contributors are their own.
Comments