I have chosen to use ansible pull mechanism as it doesn't require a controller. Also ensures that my setup is always up to date. And, my home setup can run on unreliable hardware with a small RTO (cattle NOT pet).
cd ansible
ansible-playbook -i '<hostname/ipaddress>,' ansible_pull.yml --user <username> --become --ask-become-pass
The , is required to be passed as inventory parameter, otherwise the playbook would fail.
To enable healthchecks.io monitoring for the ansible-pull cronjob, run playbook with the extra vars specified below.
ansible-playbook -i '<hostname/ipaddress>,' ansible_pull.yml --user <username> --become --ask-become-pass -e healthchecks_uuid=<checkUUID> -e config_deploy=true
To enable namecheap dynamic updates, first have your hostname registered. Then you can pass in required parameters to the pull playbook as below.
ansible-playbook -i '<hostname/ipaddress>,' ansible_pull.yml --user <username> --become --ask-become-pass -e namecheap_host=myhostname -e namecheap_domain=mydomain.tld -e namecheap_password=myrandompassword -e config_deploy=true
Once the cronjob has been setup, there should be following available services provided by the server:
- Emby
- Pihole (+Unbound)
- Grafana
- Wireguard
- Webui Aria2
- HTTPs access to services (Caddyserver, Digitalocean)
- NAS to external hdd backup - Coming soon
The whole work flow and repo is integrated with:
- Github Actions to perform some actions that I'm too lazy to perform, linting and checks
- healthchecks.io to monitor ansible-pull cronjob status