Tobias J. Endres
f01c0fa045
Ahoy! This be a finer design for our fleet of roles. Instead of a central decree, each role now opens its own ports, as a proper captain should. - The Portainer role now opens port 9000 for its treasure map (web UI). - The Network role opens the main cannons (ports 80 & 443 for Nginx) and the secret communication channel (port 51820 for Wireguard). This makes our roles more modular and seaworthy for future voyages. Yarrr!
HomeCloudPlaybooks
My Ansible Playbooks live here
Podman Integration
This project has been updated to use Podman as the container runtime instead of Docker.
Key Changes:
- The
dockerrole has been removed. - A custom
podmanrole is used to install Podman,podman-compose, andpodman-docker. - Roles that deploy containers (e.g.,
network,gitea,portainer) have been adapted to use Podman-compatible commands and modules. podman-composeis used to manage multi-container applications defined inpodman-compose.j2templates.
Running Playbooks with Podman:
Ensure Podman is installed and configured on your target hosts. The playbooks will handle the installation of podman-compose and podman-docker.
Deployment Status
Network Stack on Scully: Successfully deployed! The common, podman, and network roles have been applied to Scully, establishing the core network infrastructure including Nginx Proxy Manager and WireGuard Easy.