markri/organist

Organist deployment framework

organist's Issues

Sorting git tags

Sorting the git tags:
git for-each-ref --sort=taggerdate --format '%(refname) %(taggerdate)' refs/tags

Git branches containing a slash are ignored

A branch like "feature/awesome-new-feature" is ignored, git-flow branching depends on this naming convention

Feature request: set allowed branche(s) per target

It would be good if we can set one or multiple branches that are allowed for a target.

E.g.: master is the only branch allowed to be deployed to a production environment.

Deployed branch does not show if tag has already been deployed

In an applications Dashboard, after a branch is deployed (e.g. develop) but previously a tag has been deployed, the branch name is not visible. The previous tag is still in place.

I guess it has something to do with this logic in dashboard.html.twig.

Ampersand (&) character replaced by #mysqlpw# in db password field

If you create password with a & in it, the & will be removed on deploy and replaced with #mysqlpw#. For example: If you fill in the following password in Organist: WJBF&WEUBWE the following password will be inserted in the settings.php file on the server: WJBF#mysqlpw#WEUBWE. Could be the case with all fields that are inserted like this..

Feature request: notifications of deployments

It would be nice if I could be notified of deployments that I subscribe to.

Like:

• I subscribe to notifications of target P for project X
• On each deployment, a notification gets sent to the users (my) email

Refreshing the project before a deployment takes too long

The duration it takes to refresh the project before you want to deploy can take up to a few minutes if there are many branches. It would go faster if you first select a branch that you want to deploy and then it should just checkout that branch, instead of all branches.