Comment by Brian Hines on "Automating a Django deployment: recommended tools and tips?"

CommentAutomating a Django deployment: recommended tools and tips?

Brian Hines

Web engineer

Apr 19, 2016

For something simple, running on a single box, I just use Fabric to script out anything I need. That could be as simple as doing a git pull and restarting a service via SSH. I also use it for Docker-based deployments too. For example:

CI server builds a Docker image and publishes to a private (or public) registry on merge
CI server runs a Fabric script that pulls new Docker image on server and restarts service via SSH

For things that need multiple instances, auto-scaling, and a load balancer, I use AWS exclusively. It's really easy to interact with all of their services using the official Python SDK (boto3). Again, I script all of that with Fabric, even if all I do is call AWS services, and never open an SSH connection.

This may not be the sexiest way to do things, but I've deployed several apps (Django and other Python frameworks) with this approach and it continues to get the job done for me, even with AWS.

Tim Reid

Apr 19, 2016

Thanks for your response. I've read some of the fabric docs and seen a few examples but was deterred due to the lack of python3 support. The simplicity it offers over tools such as Ansible were attractive, however. Based on your answer I'll reconsider its usefulness!

I totally understand the Python 2 support. I've been using Docker for all my local environments for a couple years and using Python 3. I use a separate Python 2 Docker container, mount my code in there and run the Fab scripts there. Then there's no crossing the streams with trying to keep Python 2 and 3 in the same environment as the app runs in its own Python 3 container.

Search Hashnode