Marty Oehme
f2e709590b
Uses php-fpm image and is served through a simple caddy server. Automatically deploys by default and can be automatically deployed with smtp e-mail sending and s3 primary object storage optionally if desired. Utilizes some necessary hackery for container ordering and startup so startup is relatively slow (takes around 2-5 minutes at least) but once running should be stable and uninterrupted. Implements health-checks for all involved containers. Switch apache for php-fpm image |
||
|---|---|---|
| group_vars | ||
| host_vars | ||
| roles | ||
| .gitignore | ||
| ansible.cfg | ||
| inv-dev.yml | ||
| inv-staging.yml | ||
| README.md | ||
| site-dev.yml | ||
| site.yml | ||
| Vagrantfile | ||
Cloudserve infrastructure
Testing
This repository comes with a test-ready setup to try out the complete site setup locally.
It uses vagrant to accomplish this and create a pretend target host.
Install vagrant on your system and to make tests repeatable also install the vagrant plugins vagrant-hosts and vagrant-hostsupdater,
which will set a static IP for the vagrant host to be reachable under.
vagrant plugin install vagrant-hosts vagrant-hostsupdater
Then you are ready to run the complete infrastructure setup locally,
simply by executing ansible-playbook site.yml.
You can of course pick and choose what should be executed with host limits, tags, group variables, and so on,
but this should provide an easy way to see if a) the playbook is working as intended and b) what it does is useful.
Deployment
Most variables to be changed should be set either through group_variables or host_variables.
For my deployment I have a production group under group_variables which houses both a vars.yml containing basic variables
(like server_domain, caddy_email, etc.)
and a vault.yml which houses everything that should ideally not be lying around in plain-text
(individual container and database passwords for the various roles etc).
To create such a file you can do ansible-vault create group_vars/<group-name>/vault.yml or
do ansible-vault edit group_vars/<group-name>/vault.yml to edit it.
Look into the default/main.yml files of the various roles to see which variables should be set or can be overridden.
The README.md files of the roles should also carry enough information about the individual variables to make sense.