.. _fabric-commands:

Available Fabric commands
=========================

.. versionadded:: 2.5

   Starting in this release, Pootle includes Fabric deployment scripts.

The sample Fabric scripts provide several commands that you can use to easily
deploy your Pootle site.

.. note:: Most of the examples in this section will use the ``production``
   environment, but remember that other environments can be used as well.


.. _fabric-commands#bootstrap:

bootstrap
---------

This command:

- Creates the required directories, asking to remove them first if they already
  exist
- Creates a virtual environment (virtualenv) and activates it
- Clones the Pootle repository from GitHub
- Checks out the specified branch, using master if no branch is specified
- Installs the deployment requirements as listed in :file:`requirements/`,
  including the base requirements as well

.. note:: While running it may ask for the remote server ``root`` password,
   or more likely the ``sudo`` password, which is the standard password for the
   remote user configured in the environment.

.. note::
   .. versionchanged:: 2.5.1 Added support for bootstrapping from a given
      branch on Pootle repository.

Examples:

.. code-block:: bash

    $ fab production bootstrap  # Call that will use the default 'master' branch
    $ fab production:branch=stable/2.5.0 bootstrap  # Call which provides a branch


.. _fabric-commands#compile-translations:

compile_translations
--------------------

This command:

- Compiles the MO files for Pootle translations

Examples:

.. code-block:: bash

    $ fab production compile_translations


.. _fabric-commands#create-db:

create_db
---------

.. versionadded:: 2.5.1

This command:

- Creates a new blank database using the settings provided to Fabric in the
  chosen environment

.. note:: While running it may ask for the remote server ``root`` password or
   the ``sudo`` password (standard password for the remote user configured in
   the environment) as well as the specified ``db_user`` and/or database root
   password.  See the :ref:`mysql_conf <fabric-commands#mysql-conf>` command
   for a way to eliminate the need for database password prompting.

.. note:: This command will try to create a database on MySQL, which will fail
   if MySQL is not installed or the settings don't provide configuration data
   for creating the database.

Examples:

.. code-block:: bash

    $ fab production create_db


.. _fabric-commands#deploy:

deploy
------

This command:

- Calls the :ref:`update_code <fabric-commands#update-code>` command
- Calls the :ref:`syncdb <fabric-commands#syncdb>` command
- Calls the :ref:`migratedb <fabric-commands#migratedb>` command
- Calls the :ref:`deploy_static <fabric-commands#deploy-static>` command
- Calls the :ref:`install_site <fabric-commands#install-site>` command

.. note:: While running it may ask for the remote server ``root`` password or
   the ``sudo`` password (standard password for the remote user configured in
   the environment).

.. note::
   .. versionchanged:: 2.5.1 Added support for deploying from a given branch
      on Pootle repository.

Examples:

.. code-block:: bash

    $ fab production deploy  # Call that will use the default 'master' branch
    $ fab production:branch=stable/2.5.0 deploy  # Call which provides a branch


.. _fabric-commands#deploy-static:

deploy_static
-------------

This command:

- Creates :file:`pootle/assets/` directory if it does not exist
- Runs :ref:`collectstatic --noinput --clear <commands#collectstatic>` to
  collect the static files
- Runs :ref:`assets build <commands#assets>` to create the assets

Examples:

.. code-block:: bash

    $ fab production deploy_static


.. _fabric-commands#disable-site:

disable_site
------------

This command:

- Disables the Pootle site on Apache using the Apache :command:`a2dissite`
  command

.. note:: While running it may ask for the remote server ``root`` password or
   the ``sudo`` password (standard password for the remote user configured in
   the environment).

Examples:

.. code-block:: bash

    $ fab production disable_site


.. _fabric-commands#drop-db:

drop_db
---------

.. versionadded:: 2.5.1

This command:

- Drops a database (losing all data!) using the settings provided to
  Fabric in the chosen environment

.. note:: While running it may ask for the remote server ``root`` password or
   the ``sudo`` password (standard password for the remote user configured in
   the environment) as well as the specified ``db_user`` and/or database root
   password.  See the :ref:`mysql_conf <fabric-commands#mysql-conf>` command
   for a way to eliminate the need for database password prompting.

Examples:

.. code-block:: bash

    $ fab production drop_db


.. _fabric-commands#dump-db:

dump_db
-------

.. versionadded:: 2.5.1

This command:

- Dumps the database to the provided filename using the :command:`mysqldump`
  command
- Downloads the dumpfile to the local computer

.. note:: While running it may ask for the remote server ``root`` password or
   the ``sudo`` password (standard password for the remote user configured in
   the environment) as well as the specified ``db_user`` and/or database root
   password.  See the :ref:`mysql_conf <fabric-commands#mysql-conf>` command
   for a way to eliminate the need for database password prompting.

.. note:: This commands can be used to perform periodic backups, that can be
   imported later using the :ref:`load_db <fabric-commands#load-db>`
   command.

Available arguments:

``dumpfile``
  The local filename for the file where the database will be dumped.

  Default: ``pootle_DB_backup.sql``.

Examples:

.. code-block:: bash

    $ fab production dump_db  # Call that will use the default filename
    $ fab production dump_db:dumpfile=backup_mysql.sql  # Call which provides a filename


.. _fabric-commands#enable-site:

enable_site
-----------

This command:

- Enables the Pootle site on Apache using the Apache :command:`a2ensite`
  command

.. note:: While running it may ask for the remote server ``root`` password or
   the ``sudo`` password (standard password for the remote user configured in
   the environment).

Examples:

.. code-block:: bash

    $ fab production enable_site


.. _fabric-commands#initdb:

initdb
------

.. versionadded:: 2.5.1

This command:

- Runs :ref:`initdb <commands#initdb>` to initialize the database

Examples:

.. code-block:: bash

    $ fab production initdb


.. _fabric-commands#install-site:

install_site
------------

This command:

- Calls the :ref:`update_config <fabric-commands#update-config>` command
- Calls the :ref:`enable_site <fabric-commands#enable-site>` command

.. note:: While running it may ask for the remote server ``root`` password or
   the ``sudo`` password (standard password for the remote user configured in
   the environment).

Examples:

.. code-block:: bash

    $ fab production install_site


.. _fabric-commands#load-db:

load_db
-------

.. versionadded:: 2.5.1

This command:

- Uploads the given SQL dump file to the remote server
- Imports it to the database specified on Fabric settings using the
  :command:`mysql` command

.. note:: While running it may ask for the remote server ``root`` password or
   the ``sudo`` password (standard password for the remote user configured in
   the environment) as well as the specified ``db_user`` and/or database root
   password.  See the :ref:`mysql_conf <fabric-commands#mysql-conf>` command
   for a way to eliminate the need for database password prompting.

.. note:: You must first create the database you will import (e.g. using the
   :ref:`create_db <fabric-commands#create-db>` command) before calling this
   command,

Available arguments:

``dumpfile``
  The local SQL dump filename that will be uploaded to the remote server and
  imported into an existing database on the remote server. This file can be
  created using the :ref:`dump_db <fabric-commands#dump-db>` command.

  .. note:: This is a required argument.

Examples:

.. code-block:: bash

    $ fab production create_db  # Remember to create the DB first
    $ fab production load_db:dumpfile=backup_mysql.sql


.. _fabric-commands#migratedb:

migratedb
---------

.. versionadded:: 2.5.1

This command:

- Runs :ref:`migrate <commands#migrate>` to update the 2.5 or later database
  schema to the latest version

Examples:

.. code-block:: bash

    $ fab production migratedb


.. _fabric-commands#mysql-conf:

mysql_conf
----------

.. versionadded:: 2.5.1

This command creates a :file:`.my.cnf` MySQL options file on the remote system
with the password(s) for database access stored in them (the passwords are
taken from the :file:`fabric.py` settings file).  Once you have done this, you
can un-comment the alternate ``db_password_opt`` and ``db_root_password_opt``
settings in :file:`fabric.py`, which will eliminate the need for password
prompting on all MySQL operations.

Examples:

.. code-block:: bash

    $ fab production mysql_conf


.. _fabric-commands#production:

production
----------

This command:

- Sets up the configuration for the ``production`` environment in Fabric
  settings

.. note:: This command is useless unless it is called before another command or
   commands.

.. note:: This command allows changing the settings. To do so just pass it any
   of its arguments when calling it.

   Note that some commands might require passing any or all of these arguments
   to this command in order to overwrite the default settings before calling
   those commands. For example the command :command:`stage_feature` requires
   passing :option:`branch`, :option:`repo` and :option:`feature`.

.. note::
   .. versionchanged:: 2.5.1 Added support for altering the settings based on
      the passed arguments.

Available arguments:

``branch``
  A specific branch to check out in the repository.

``repo``
  A repository URL to clone from.

  This allows to checkout from a fork repository (not necessarily on GitHub)
  and try new features developed on that repository. It must be an URL that the
  ``git clone`` command is able to clone.

``feature``
  Allows specifying if the deployment is for a feature-staging server. Such
  servers are used by Pootle developers in order to allow quick test of new
  features using a live Pootle server.

Examples:

.. code-block:: bash

    $ fab production bootstrap

In the previous example :command:`production` is called to set up the
environment for calling :command:`bootstrap` afterwards.

.. code-block:: bash

    $ fab production:branch=feature/extension-actions bootstrap

In the previous example :command:`production` is called to set up the
environment for calling :command:`bootstrap` afterwards.

The :option:`branch` argument overwrites the default branch in the settings,
which are then used for all the subsequent commands (just :command:`bootstrap`
in this example).

.. code-block:: bash

    $ fab production:branch=feature/extension-actions,repo=git://github.com/unho/pootle.git bootstrap

In the previous example :command:`production` is called to set up the
environment for calling :command:`bootstrap` afterwards.

The :option:`branch` and :option:`repo` arguments overwrite the default
settings, which are then used for all the subsequent commands (just
:command:`bootstrap` in this example).

.. code-block:: bash

    $ fab production:branch=feature/extension-actions,repo=git://github.com/unho/pootle.git,feature=yes stage_feature

This example is like the previous one, with the addition of the
:option:`feature` argument that triggers the altering of several settings. That
altering is necessary for working with feature-staging servers.


.. _fabric-commands#setup:

setup
-----

.. versionadded:: 2.5.1

This command:

- Runs :ref:`setup <commands#setup>` to create or upgrade the database as
  required

Examples:

.. code-block:: bash

    $ fab production setup


.. _fabric-commands#setup-db:

setup_db
--------

.. versionadded:: 2.5.1

This command:

- Runs :ref:`syncdb --noinput <commands#syncdb>` to create the database schema
- Runs :ref:`initdb <commands#initdb>` to populate the standard schema objects
- Runs :ref:`migrate <commands#migrate>` to bring the database schema
  up to the latest version

Examples:

.. code-block:: bash

    $ fab production setup_db


.. _fabric-commands#stage-feature:

stage_feature
-------------

.. versionadded:: 2.5.1

This command:

- Calls the :ref:`bootstrap <fabric-commands#bootstrap>` command
- Calls the :ref:`create_db <fabric-commands#create-db>` command
- Copies the data in the specified source DB into the DB that will be used for
  the deployed Pootle
- Calls the :ref:`update_db <fabric-commands#update-db>` command
- Calls the :ref:`deploy_static <fabric-commands#deploy-static>` command
- Calls the :ref:`install_site <fabric-commands#install-site>` command

.. note:: While running it may ask for the remote server ``root`` password and
   the specified ``db_user`` password.

.. note:: This command is intended primarily for deploying ad-hoc Pootle
   servers for easing the test of feature branches during Pootle development.

.. warning:: This command might require changing the **source_db** field in the
   :file:`deploy/ENVIRONMENT/fabric.py` file. Note that the database specified
   on this field must exist.

.. warning:: This command requires using the ``staging`` environment passing to
   it the :option:`feature` argument, the desired branch and optionally a
   repository URL.

Examples:

.. code-block:: bash

    $ fab staging:branch=feature/extension-actions,feature=yes stage_feature
    $ fab staging:branch=feature/extension-actions,repo=git://github.com/unho/pootle.git,feature=yes stage_feature


.. _fabric-commands#staging:

staging
-------

This command:

- Sets up the configuration for the ``staging`` environment in Fabric settings

.. note:: This command is useless unless it is called before another command or
   commands.

.. note:: This command allows changing the settings. To do so just pass it any
   of its arguments when calling it.

   Note that some commands might require passing any or all of these arguments
   to this command in order to overwrite the default settings before calling
   those commands. For example the command :command:`stage_feature` requires
   passing :option:`branch`, :option:`repo` and :option:`feature`.

.. note::
   .. versionchanged:: 2.5.1 Added support for altering the settings based on
      the passed arguments.

Available arguments:

``branch``
  A specific branch to check out in the repository.

``repo``
  A repository URL to clone from.

  This allows to checkout from a fork repository (not necessarily on GitHub)
  and try new features developed on that repository. It must be an URL that the
  ``git clone`` command is able to clone.

``feature``
  Allows specifying if the deployment is for a feature-staging server. Such
  servers are used by Pootle developers in order to allow quick test of new
  features using a live Pootle server.

Examples:

.. code-block:: bash

    $ fab staging bootstrap

In the previous example :command:`staging` is called to set up the environment
for calling :command:`bootstrap` afterwards.

.. code-block:: bash

    $ fab staging:branch=feature/extension-actions bootstrap

In the previous example :command:`staging` is called to set up the environment
for calling :command:`bootstrap` afterwards.

The :option:`branch` argument overwrites the default branch in the settings,
which are then used for all the subsequent commands (just :command:`bootstrap`
in this example).

.. code-block:: bash

    $ fab staging:branch=feature/extension-actions,repo=git://github.com/unho/pootle.git bootstrap

In the previous example :command:`staging` is called to set up the environment
for calling :command:`bootstrap` afterwards.

The :option:`branch` and :option:`repo` arguments overwrite the default
settings, which are then used for all the subsequent commands (just
:command:`bootstrap` in this example).

.. code-block:: bash

    $ fab staging:branch=feature/extension-actions,repo=git://github.com/unho/pootle.git,feature=yes stage_feature

This example is like the previous one, with the addition of the
:option:`feature` argument that triggers the altering of several settings. That
altering is necessary for working with feature-staging servers.


.. _fabric-commands#syncdb:

syncdb
------

.. versionadded:: 2.5.1

This command:

- Runs :ref:`syncdb --noinput <commands#syncdb>` to create the database schema

Examples:

.. code-block:: bash

    $ fab production syncdb


.. _fabric-commands#touch:

touch
-----

This command:

- Reloads daemon processes by touching the WSGI file

Examples:

.. code-block:: bash

    $ fab production touch


.. _fabric-commands#unstage-feature:

unstage_feature
---------------

.. versionadded:: 2.5.1

This command:

- Calls the :ref:`disable_site <fabric-commands#disable-site>` command
- Calls the :ref:`drop_db <fabric-commands#drop-db>` command
- Removes the configuration files created by the :ref:`update_config
  <fabric-commands#update-config>` command
- Removes the directories created during the deployment, including the ones
  holding the translation files and the repositories for those translation
  files

.. note:: While running it may ask for the remote server ``root`` password and
   the specified ``db_user`` password.

.. note:: This command is intended for removing Pootle deployments performed
   using the :ref:`stage_feature <fabric-commands#stage-feature>` command.

.. warning:: This command requires using the ``staging`` environment passing to
   it the :option:`feature` argument and the desired branch.

Examples:

.. code-block:: bash

    $ fab staging:branch=feature/extension-actions,feature=yes unstage_feature


.. _fabric-commands#update-code:

update_code
-----------

This command:

- Updates the Pootle repository from GitHub
- Checks out the specified branch, using master if no branch is specified
- Updates the deployment requirements as listed in :file:`requirements/`,
  including the base requirements as well

.. note::
   .. versionchanged:: 2.5.1 Added support for updating code from a given branch
      on Pootle repository.

Examples:

.. code-block:: bash

    $ fab production update_code  # Call that will use the default 'master' branch
    $ fab production:branch=stable/2.5.0 update_code  # Call which provides a branch


.. _fabric-commands#update-config:

update_config
-------------

This command:

- Will upload the configuration files included in the chosen environment to the
  remote server:

  - Configure VirtualHost using the provided :file:`virtualhost.conf`
  - Configure WSGI application using the provided :file:`pootle.wsgi`
  - Configure and install custom settings for Pootle using the provided
    :file:`settings.conf`

.. note:: While running it may ask for the remote server ``root`` password or
   the ``sudo`` password (standard password for the remote user configured in
   the environment).

Examples:

.. code-block:: bash

    $ fab production update_config


.. _fabric-commands#update-db:

update_db
---------

This command:

- Runs :ref:`updatedb <commands#updatedb>` and :ref:`migrate
  <commands#migrate>` to update the database schema to the latest version

Examples:

.. code-block:: bash

    $ fab production update_db


.. _fabric-commands#upgrade:

upgrade
-------

.. versionadded:: 2.5.1

This command:

- Runs :ref:`upgrade <commands#upgrade>` to apply any special
  post-schema-upgrade actions (including changes needed for updated Translate
  Toolkit version).  This would typically be performed after running the
  :ref:`update_code <fabric-commands#update-code>` command. If you haven't
  just upgraded Pootle or the Translate Toolkit to a new release, this isn't
  generally required, so there is no need to run it unless release notes or
  other instructions direct you to do so.

Examples:

.. code-block:: bash

    $ fab production upgrade
