Available commands and how to use them

Commands are separated into two grops:

• Project: commands for setting up and managing Plone/Python projects
• Server: commands for setting up and managing servers

Project commands

niteoweb.fabfile.project.configure_nginx(shortname=None)

Upload Nginx configuration for this site to /etc/nginx/sites-available and enable it so it gets included in the main nginx.conf.

niteoweb.fabfile.project.download_code(shortname=None, prod_user=None, svn_params=None, svn_url=None, svn_repo=None, svn_dir=None)

Pull project code from code repository.

niteoweb.fabfile.project.download_data()

Download Zope’s Data.fs from the server.

niteoweb.fabfile.project.enable_nginx_config(shortname=None)

Make a link from sites-available/ to sites-enabled/ and reload Nginx.

niteoweb.fabfile.project.prepare_buildout(prod_user=None, python_version=None, production_cfg=None)

Prepare zc.buildout environment so we can use bin/buildout -c production.cfg to build a production environment.

niteoweb.fabfile.project.run_buildout(prod_user=None, production_cfg=None)

Run bin/buildout -c production.cfg in production user’s home folder on the production server.

niteoweb.fabfile.project.start_supervisord(prod_user=None)

Start supervisord process monitor which in turn starts Zope and optionally others (Varnish, HAProxy, etc.).

niteoweb.fabfile.project.supervisorctl(*cmd)

Runs an arbitrary supervisorctl command.

niteoweb.fabfile.project.upload_blobs(prod_user=None, path=None)

Upload BLOB part of Zope’s data to the server.

niteoweb.fabfile.project.upload_data(prod_user=None)

Upload Zope’s data to the server.

niteoweb.fabfile.project.upload_nginx_config(shortname=None, nginx_conf=None)

Upload Nginx configuration to /etc/nginx/sites-available.

niteoweb.fabfile.project.upload_sphinx(hq_ip=None, sphinx_dir=None, path=None)

Uploads HTML files generated by Sphinx.

niteoweb.fabfile.project.upload_zodb(prod_user=None, path=None)

Upload ZODB part of Zope’s data to the server.

Server commands