Ep183: Django Deployments in 2025 with Eric Matthes is now live!
Eric is the author of Python Crash Course, the Mostly Python newsletter, and the django-simple-deploy package. We talk about rewriting the Django deployment story, different hosting providers, and teaching Python & Django to newcomers.
https://djangochat.com/episodes/django-deployments-in-2025-eric-matthes-hdOwWv2h
@djangochat This was a fun conversation!
I gave a lightning talk at PyCon US that included a live demo, held an open space about the project, and stayed for three days of sprints.
There's good energy around the project, and I think we'll see a growing set of plugins for different platforms, and different approaches to deployment.
Thanks for the invitation!
@carlton @djangochat Sprints were fun! It was mostly people interested in writing plugins that support deployment approaches I've never used.
"I'm here to put terraform into this project! How do I get started?!"
I just showed them how to generate a new plugin, and showed them where to start writing their own platform-specific code. It was pretty fun to watch!
@_chrismay was interested in writing a VPS plugin, and his demo of the 0.1.0 version of dsd-vps worked the first time he tried it. :)
@ehmatthes @djangochat @_chrismay Rock on! 🙌
I saw you tooting about a Flask version too... — You'll have to rename it to world-domination-simple-deploy 😉
@carlton @djangochat @_chrismay The flask work felt like a side quest I should step away from, but it was really helpful to build a tiny working version. It ended up giving me a fresh perspective on this project after so long. How would I approach this project if I had a blank slate?
@offby1 brought up some difficult naming issues. To many people, "deployment" is ongoing. So the name django-simple-deploy doesn't match its behavior. django-initial-deploy might be better, but still not perfect.
@carlton @djangochat @_chrismay @offby1 I'm going to add a glossary, so it's easier to clarify what's meant by terms like "deploy", and "configure". There's "provisioning" as well.
I'm not sure you could come up with a perfect naming system. When most people find themselves in front of a working project on their local system for the first time, and they want to get it in front of others, we all say they need to "deploy" their project.
So I think the name still mostly fits.
@carlton @djangochat @_chrismay @offby1 One of my summer goals is to take the flask-simple-deploy to the point where it can support a project with a database. Then we can have this conversation about what we want deployment tools in these two frameworks to look like.
A shared conversation sounds nice. :)
@ehmatthes @carlton @djangochat @_chrismay @offby1
interesting conversation, i am yet to listen but i have a good issue suggestion for dsd or flask-simple-deploy 🤣
would really love to see support for not-so-well known PAAS for django, maybe a general flow for ubuntu Virtual machines: e.g ec2, compute engines(gcp) and such …
@chrisdevcode @carlton @djangochat @_chrismay @offby1 I've been working on a plugin for deployment to a generic VPS. It started as dsd-digitialocean, then I realized it should work for any VPS provider. So dsd-vps was born:
@ehmatthes @carlton @djangochat @_chrismay @offby1
perfect, thanks for sharing this.
Django Chat Podcast
The B is Silent
Eric Matthes
Carlton Gibson 🇪🇺
Chris Achinga