Deploying a Django app on AWS: Difference between revisions

From Littledamien Wiki
Jump to navigation Jump to search
No edit summary
Line 10: Line 10:
* See [[Amazon_Web_Services_Website_Hosting_Fundamentals#AWS_services|AWS Services]]
* See [[Amazon_Web_Services_Website_Hosting_Fundamentals#AWS_services|AWS Services]]
* See [[Django App Prerequisites for AWS Elastic Beanstalk]]
* See [[Django App Prerequisites for AWS Elastic Beanstalk]]
== AWS Elastic Beanstalk ==
Existing Elastic Beanstalk applications and environments can be found in the [https://us-west-2.console.aws.amazon.com/elasticbeanstalk/home AWS Elastic Beanstalk management console].
Create a ne Elastic Beanstalk application from the command line one a local workstation,
<syntaxhighlight lang="bash">
$ eb init
</syntaxhighlight>
This will prompt for region, credentials, application name, python version, ssh availability, etc.
Create a new Elastic Beanstalk environment from the command line on a local workstation.
<syntaxhighlight lang="bash">
$ eb create --database.engine postgres
</syntaxhighlight>
This will prompt for the environment name, its URL prefix, and a database username and password.
The `--database.engine` argument is optional.


== Deploying a Django app ==
== Deploying a Django app ==

Revision as of 01:49, 10 February 2016

Overview

All of these steps are performed locally.

Prerequisites

I didn't realize this at first, but these prerequisites are all local. The first time I tried this out, I thought I had to get on a remote server to install Python, Django, awsebcli, etc. All of these things are installed on the local workstation and eb deploy handles moving them over and replicating the app environment.

AWS Elastic Beanstalk

Existing Elastic Beanstalk applications and environments can be found in the AWS Elastic Beanstalk management console.

Create a ne Elastic Beanstalk application from the command line one a local workstation,

$ eb init

This will prompt for region, credentials, application name, python version, ssh availability, etc.

Create a new Elastic Beanstalk environment from the command line on a local workstation.

$ eb create --database.engine postgres

This will prompt for the environment name, its URL prefix, and a database username and password.

The --database.engine argument is optional.

Deploying a Django app

Updates to the app are deployed with eb deploy.

This looks at .elasticbeanstalk/config.yml for the target application and environment.

branch-defaults:
  master:
    environment: nrose-env
global:
  application_name: north-rose
  default_ec2_keyname: nrosedevs-aws
  default_platform: 64bit Amazon Linux 2015.09 v2.0.6 running Python 3.4
  default_region: us-west-2
  profile: eb-cli
  sc: git

With the master Git branch checked out, and the config.yml above, eb deploy will package up the project file and upload them to the EC2 instance corresponding with the nrose-env environment of the north-rose app.

To update a staging environment, edit config.yml with the following:

branch-defaults:
  master:
    environment: nrose-env
  staging:
    environment: nrose-staging

With the staging Git branch checked out, eb deploy will now update the nrose-staging environment.

Alternatively, use eb deploy alternate-env to target a non-default EB environment named alternate-env.

Installing Django app dependencies

See Defining Django App Dependencies

Notes

See also

References