ansible-playbooks/roles/tasks/debian
2024-11-07 18:54:42 +08:00
..
README.md Update scripts 2024-10-29 02:11:53 +08:00
setup.yml Omit use of tmux in playbooks for more verbose error handling 2024-11-07 18:54:42 +08:00
start_backups.yml Omit use of tmux in playbooks for more verbose error handling 2024-11-07 18:54:42 +08:00
start_services.yml Omit use of tmux in playbooks for more verbose error handling 2024-11-07 18:54:42 +08:00
update.yml Omit use of tmux in playbooks for more verbose error handling 2024-11-07 18:54:42 +08:00

Usage

Setup

  1. Run setup.yml using a non-sudo user, providing regular and sudo credentials.
ansible-playbook roles/tasks/debian/setup.yml -u keannu125 -k --ask-become-pass

This will elevate to root user via sudo and set up root SSH access through the provided id_rsa.pub file in the control node's own .ssh directory.

  1. Set up the necessary template scripts provided at /root/scripts.

  2. Rename .env.sample to .env. (via mv .env.sample .env).

  3. Provide your ACME SSL access tokens in the .env for renew_ssl.sh to parse.

  4. Also provide your ACME_EMAIL in debian.yml under group_vars for the playbook to parse.

  5. Provide project directories to spin up on boot through start_services.sh.

  6. Provide the same project directories to back up via Borg in backup.sh including any file/folder exemptions.

  7. Update the Samba credentials file located at /root/.samba/credentials.

# credentials
user=USERNAME
password=PASSWORD
  1. Update the CIFS/Samba mount for backups located in crontab (via crontab -e).
# crontab entry
* * * * * mount.cifs "//255.255.255.0/SAMBA-MOUNT" "/mnt/backups" -o credentials="/root/.samba/credentials"

If you'd need to run the setup.yml playbook again for any reason. You can omit specifying user or sudo credentials and simply run.

ansible-playbook roles/tasks/debian/setup.yml

Any existing or additional scripts that have already been modified will not be overwritten (See force: false directives in setup.yml).