but one option that many Django developers enjoy is Fabric. Below, and in the following sections, we’ll show off a few example fabfiles (i.e. Fabric scripts) that automate these file deployment options options. The syntax of a fabfile is fairly straightforward but won’t be covered here; consult Fabric’s documentation, for a complete explanation of the syntax. So, a fabfile to deploy static files to a couple like: 4.16. Deploying static files 589 Django Documentation, Release 1.8.20.dev20180306181007 from fabric.api import * # Hosts to deploy onto env.hosts = ['www1.example.com', 'www2.example.com'] # Where

but one option that many Django developers enjoy is Fabric. Below, and in the following sections, we’ll show off a few example fabfiles (i.e. Fabric scripts) that automate these file deployment options covered here; consult Fabric’s documentation, for a complete explanation of the syntax. So, a fabfile to deploy static files to a couple of web servers might look something like: from fabric.api import * # bits of static files that have changed. Here’s how this might look in a fabfile: from fabric.api import * from fabric.contrib import project # Where the static files get collected locally. Your STATIC_ROOT

but one option that many Django developers enjoy is Fabric. Below, and in the following sections, we’ll show off a few example fabfiles (i.e. Fabric scripts) that automate these file deployment options covered here; consult Fabric’s documentation, for a complete explanation of the syntax. So, a fabfile to deploy static files to a couple of web servers might look something like: from fabric.api import * # bits of static files that have changed. Here’s how this might look in a fabfile: from fabric.api import * from fabric.contrib import project # Where the static files get collected locally. Your STATIC_ROOT

but one option that many Django developers enjoy is Fabric. Below, and in the following sections, we’ll show off a few example fabfiles (i.e. Fabric scripts) that automate these file deployment options covered here; consult Fabric’s documentation, for a complete explanation of the syntax. So, a fabfile to deploy static files to a couple of web servers might look something like: from fabric.api import * # bits of static files that have changed. Here’s how this might look in a fabfile: from fabric.api import * from fabric.contrib import project # Where the static files get collected locally. Your STATIC_ROOT

but one option that many Django developers enjoy is Fabric. Below, and in the following sections, we’ll show off a few example fabfiles (i.e. Fabric scripts) that automate these file deployment options covered here; consult Fabric’s documentation, for a complete explanation of the syntax. So, a fabfile to deploy static files to a couple of web servers might look something like: from fabric.api import * # bits of static files that have changed. Here’s how this might look in a fabfile: from fabric.api import * from fabric.contrib import project # Where the static files get collected locally. Your STATIC_ROOT

but one option that many Django developers enjoy is Fabric. Below, and in the following sections, we’ll show off a few example fabfiles (i.e. Fabric scripts) that automate these file deployment options covered here; consult Fabric’s documentation, for a complete explanation of the syntax. So, a fabfile to deploy static files to a couple of web servers might look something like: from fabric.api import * # bits of static files that have changed. Here’s how this might look in a fabfile: from fabric.api import * from fabric.contrib import project # Where the static files get collected locally. Your STATIC_ROOT