More Django AWS deployment thoughts
Billy Fung / 2018-06-23
One of the easy and nice things about full featured frameworks is that they’re usually first rate customers when it comes to pipeline solutions. Such is the case for Amazon Elastic Beanstalk, which is an offering that sets up web applications easily. This means setting up the application server, the database, the static file storage, the traffic balancer; all the infrastructure that is needed to have an application that is ready for scale.
Going back a bit, I’ve been working on a Django application for a couple weeks now. With all development projects, it’s pretty easy to set up a local environment and write code and test it. But the next step is the deploy the application to somewhere that isn’t just your local computer. For me, this meant using an EC2 instance, linked to Postgres on RDS, and then also having logs and a load balancer for the future. The main reason that I chose to use ELB instead of just having an EC2 copy the source is that I want to set up a continuous integration server to run tests.
I didn’t really have anything conscious to say in this blog post, but just that I’ve been working and finishing up deploying a Django application with ELB and it was quite painfree.