Releases: caktus/margarita
v1.7.2
v1.7.1
Force reset the letsencrypt repo, so that the changes that letsencrypt's built-in updater makes doesn't cause the deployment to fail.
v1.7.0
-
Pin global pip to 8.1.1 to avoid Salt incompatibility.
.. IMPORTANT::
If your deploy is currently broken because you have run a deploy with a version of Margarita
less than 1.7.0, then run the following command first::$ fab staging salt:"cmd.run 'pip install pip\=\=8.1.1'" # Yes, the backquotes are needed!
Then, update your
margarita_version
to 1.7.0 and deploy::$ fab staging deploy
v1.6.8
v1.6.7
- Allow specifying the branch to deploy in the 'branch' pillar variable.
-
NOTE: These changes are fully backwards compatible; no pillar changes
are required to update but structure simplifications are now possible. -
Most projects will be able to specify the repo just once, in
project.sls
:repo: url: [email protected]/user/project.git
-
Projects which deploy the
master
branch to their production
environments may only need to change thebranch
pillar in their
staging environments:branch: develop
-
With this structure, the deploy branch can be easily overridden from
the command line:salt '*' -l info highstate pillar='{"branch": "hotfix"}'
Corresponding changes in caktus/django-project-template show how
this can be used to deploy a non-default branch using Fabric with no
need to edit the pillar file.For more info, see the Salt documentation:
https://docs.saltstack.com/en/latest/topics/pillar/#set-pillar-data-at-the-command-line
-
v1.6.6
v1.6.5
v1.6.4
- Option to use letsencrypt.org to get certificates for sites by setting
letsencrypt: true
.
See also the documentation.
v.1.6.3
v1.5.0
- Added a state (
watchlog
) that allows you to forward any plain text log to syslog. - Don't run
apt-get update
on every package install, speeding up deploys. - Don't install NewRelic plugin unless we have a NewRelic key.
- Fix NPM state and include it so that salt runs it.