hosting/cloudserve-infrastructure
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
A complete ansible infrastructure for my personal server. Hosts a variety of FOSS applications through docker deployments within individual ansible roles.
33 commits 1 branch 0 tags 408 KiB
Find a file
Marty Oehme 7eeeec0489
Move caddy API access to internal variables 
Moved the ability to switch off caddy's api access to variables not
intended to be overwritten. It still can, but it is much more difficult.
Since every docker deployment relies on caddy's api to be accessible it
seems weird to present an easily reachable option to turn it off
globally.
2021-10-21 14:25:54 +02:00
group_vars Rename domain group variable to server_domain 2021-10-08 10:03:27 +02:00
host_vars Add testing inventory and group variables 2021-07-29 15:11:28 +02:00
roles Move caddy API access to internal variables 2021-10-21 14:25:54 +02:00
.gitignore Add staging and development environments 2021-10-21 14:23:26 +02:00
ansible.cfg Add staging and development environments 2021-10-21 14:23:26 +02:00
inv-dev.yml Add staging and development environments 2021-10-21 14:23:26 +02:00
inv-staging.yml Add staging and development environments 2021-10-21 14:23:26 +02:00
README.md Add testing inventory and group variables 2021-07-29 15:11:28 +02:00
site-dev.yml Add staging and development environments 2021-10-21 14:23:26 +02:00
site.yml Make sure curl is installed for the hacky reverse proxy 2021-07-30 00:46:06 +02:00
Vagrantfile Fix docker python module installation for sudo 2021-07-27 12:54:32 +02:00

README.md

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. So, install vagrant on your system and to make tests repeatable also install the vagrant plugins vagrant-hosts and vagrant-hostsupdater.

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.