Makesite deploy options are specified on the command line and configuration files.
Makesite configuration files in INI format and must have a makesite.ini name. Each can contain two sections: Main and Templates. Section Main contain project deploy options. Section Templates contain custom templates paths.
The configuration files are loaded in the fololowing order:
Settings from each next configuration file owerwrites previous.
Path to projects dir, required if not set $MAKESITE_HOME. Saved in makesite_home variable.
Deployed branch of project, default is ‘master’. Saved in branch variable.
One or more template names separated by commas. Saved in template variable.
Path to custom config file.
Deploy makesite built-in module.
Source path. VCS address starts with prefix: git+git://github.com/... Saved in src variables.
Note
In options you can use variables from command line and deploy_dir:
domain=%(branch)s.%(project)s.klen.xxx
Default: db-postgres,django,zeta,uwsgi
Define deploy templates, if not exist -t
Default: www-data
Define deploy user. From him runned processes and deployed templates.
Default: www-data
Define deploy group.
Default: 80
Define deploy port, used for servers configuration.
Default: example.com
Define deploy domain name, used for servers configuration.
Default: dev
Im use it to switch django settings files ex.
# Base makesite INI file
# ==============
# Base settings
[Main]
template=db-postgres,django,zeta,uwsgi
site_user=www-data
site_group=www-data
port=80
domain=example.com
mode=dev
# This section uses for custom templates Ex. custom_name=<path_to_custom>
[Templates]
# This section uses for define alias. Ex. prod = update server.master -H web.prod.server
[alias]