jsphpl/laravan

Ansible Playbooks for Laravel - machine provisioning and app deployment

laravan's Issues

Rollback migrations when deployment fails

• How to determine if the migrations were attempted? Only roll back if so…
• Wouldn't it be more accurate to create a "follower database" for the new deployment, migrate on that one and switch dbs after successful deployment

Run cli commands (workers, post deploy, migrations, etc.) with the same php version as FPM

Add an option to backup databases before deploy

In the apps config, add an optional array of databases to backup before a deployment

Create a tag for provisioning a new app

Currently, there is no single tag that ensures everything is set up correctly, when adding a new app in apps.yml. It would be desirable to be able to run something along the lines of ansible-playbook provision.yml -e env=production --tags new-app, after having added a new app config.

Add automated tests

Ansible Galaxy, debops.ferm package not found

While running the ./setup.sh I ran into the problem that the package debops.ferm has been removed from the Ansible Galaxy.
For as far as I can find the package is still available on Github.

So would it be an easy fix to just point to the Github repo in the requirements file?

Add detailed documentation about app configuration

Apart from the example, there is currently no proper documentation on all the details:

• How to host a SPA
• How to host a non-laravel PHP project
• How to host a static site
  • define a project root
• Detailed Backups configuration
• Choosing a PHP version
• Configuring workers
• Configuring post-deploy commands
• …