fab-support 0.2.5

Implement staging in Fabric and recipes for pelican to [local, s3] and Django to Heroku.

fab_support

Code to implement staging in Fabric and recipes for using that staging for pelican deployments and Django to Heroku. It supports a local .env file importing for storing secrets that you don’t want to store in git.

Stages

Stages are the different stages of development of an application. So they might go from:

test -> uat -> production -> old production

Different stages of a single project

I have create a fab-support.py which does the heavy lifting of creating each environment. The aim is that this should be hardly any more than the use of fabric and much simpler than the use of a full featured build Salt or Ansible. This is really only if you fit one of the use cases. Like Ansible this is a simple single master deployment system.

Suitable use cases:

• Deployment of Pelican static website

  • Deployment to local file system for use with a file server

  • Deployment to local for a file based browser

  • Deployment to S3

• Simple Django to Heroku where you have at a minimum two stages eg UAT and Production.

  • Copes with Postgres database

  • Static data in AWS

In the root fabfile create a dictionary like this which documents how to deploy each stage:

from fabric.api import env

# Definition of different environments to deploy to
env['stages'] = {
    'localsite': {
        'comment': 'stage: For serving locally on this computer via mongoose. ',
        'config_file': 'local_conf.py',
        'destination': 'C:/Sites/local.drummond.info',
        'copy_method': copy_file,
        'SITEURL': 'http://localhost:8042',
    },
    'production': {
        'comment': 'stage: For serving on local file server',
        'destination': '//10.0.0.1/web/www.drummond.info',
        'config_file': 'local_conf.py',
        'copy_method': copy_file,
        'SITEURL': 'http://www.drummond.info',
},
}

Then the deployment by Pelican is pretty standardised eg build deploy and you have commands such as:

fab localsite deploy

I think it was inspired by BreytenErnsting. This is then reiplmeneted using the standard env environment and support in Fabric.

• Free software: MIT license

• Documentation: https://fab-support.readthedocs.io.

Django configuration

The Django configuration includes the following features:

• deployment to Heroku

• Celery support with aqmp

• Log trapping support with Papertrail

Features

Runs on Windows. If it is getting to complex then it should probably be ported to Ansible or Salt.

Levels of fabfile in this module

In this module I use three levels of fabfile.py:

• At the project root

• at the /tests root

• at a test/demo level

This can get confusing, however they operate at different levels. The project is about project operations eg releasing to fab_support to pypi.

The tests level is then about managing the tests. Some of these tests use fab support and a fabfile.py which gives you the third level of nesting.

Project level fabfile

This is used to do work on the distribution:

• Make deocumentation

• build wheels

• deploy wheels to the package manager

At the tests level

This is used to run local commands. Often the commands will be run from the test fab file level and then lcd to the demo level.

At the tests/demo level

This is a model fabric file- however it is not like a normal one in that fab_support is not installed in the environment and in fact is located at ../../fab_support.

Credits

This package was created with Cookiecutter and the audreyr/cookiecutter-pypackage project template. Thanks Audrey

History

0.2.1 (2018-05-11)

• Updating pelican comamnds to the parameter method of passing stage.

Note tests were failing to a non obvious cause. This was Heroku CLI needed updating to the latest version. I manually upgraded.

0.2.0 (2018-04-20)

• Change the way environment variables are passed through.

In version 0.1 only the following variables were considered env variables:

‘DJANGO_SECRET_KEY’, ‘DJANGO_ADMIN_URL’, ‘DJANGO_AWS_ACCESS_KEY_ID’, ‘DJANGO_AWS_SECRET_ACCESS_KEY’, ‘DJANGO_AWS_STORAGE_BUCKET_NAME’, ‘DJANGO_MAILGUN_API_KEY’, ‘DJANGO_SERVER_EMAIL’, ‘MAILGUN_SENDER_DOMAIN’, ‘DJANGO_ACCOUNT_ALLOW_REGISTRATION’, ‘DJANGO_SENTRY_DSN’, ‘XERO_CONSUMER_SECRET’, ‘XERO_CONSUMER_KEY’

Now there is an ‘ENV’ list of variables that allows any variables to be passed through and also for them to renamed on the way from the file .env

0.1.0 (2018-02-04)

• First release on PyPI.