From 6f37f1417f341b3e7560818b17fb8f77f0e5dbfc Mon Sep 17 00:00:00 2001 From: "Dustin C. Hatch" Date: Wed, 5 Feb 2025 21:47:50 -0600 Subject: [PATCH] site: Add master site playbook The `site.yml` playbook imports all of the other playbooks, providing a way to deploy _everything_. Normally, this would only be done for a single host, as part of its initial provisioning, to quickly apply all common configuration and any application-specific configuration for whatever roles the host happens to hold. The `host-setup.yml` playbook provides an entry point for configuring all common configuration. Basically anything we want to do to _every_ machine, regardless of its location or role. --- host-setup.yml | 5 +++++ site.yml | 13 +++++++++++++ 2 files changed, 18 insertions(+) create mode 100644 host-setup.yml create mode 100644 site.yml diff --git a/host-setup.yml b/host-setup.yml new file mode 100644 index 0000000..74bd581 --- /dev/null +++ b/host-setup.yml @@ -0,0 +1,5 @@ +- import_playbook: bootstrap.yml + +- import_playbook: collectd.yml +- import_playbook: promtail.yml +- import_playbook: auto-updates.yml diff --git a/site.yml b/site.yml new file mode 100644 index 0000000..ba76b45 --- /dev/null +++ b/site.yml @@ -0,0 +1,13 @@ +- import_playbook: host-setup.yml + +- import_playbook: fileserver.yml +- import_playbook: frigate.yml +- import_playbook: gitea.yml +- import_playbook: jellyfin.yml +- import_playbook: kubernetes.yml +- import_playbook: minio-backups.yml +- import_playbook: minio.yml +#- import_playbook: nextcloud.yml +- import_playbook: postgresql.yml +- import_playbook: serterm.yml +- import_playbook: smtp-relay.yml