Deployment Plan for Home Cloud

1. Goal

The goal is to set up a personal cloud environment on your two hosts, Mulder and Scully. This involves deploying Gitea (a self-hosted Git service) on Mulder, and Keycloak (an identity and access management solution) on Scully. All services should be accessible via HTTPS with Let's Encrypt certificates and subdomain-based routing. We will also set up a WireGuard VPN with a web interface for secure access to your network.

2. Phased Deployment Plan

Phase 1: Network Infrastructure on Scully (Current Focus)

Goal: Deploy the common and network roles on Scully. The network role will set up Nginx Proxy Manager (for HTTPS and subdomain routing) and WireGuard Easy (for VPN with web UI).
Host and Role Assignments:
- Scully: common, network
Configuration Files:
- inventory/hosts.yml: Defines Mulder and Scully, their connection details, and role-specific variables.
- playbooks/main.yml: Modified to execute the common and network roles on Scully.
- group_vars/all.yml: Contains common variables like the domain name and service credentials.
Execution Plan:
1. Perform a dry run of the playbook to deploy the common and network roles on Scully.
2. If the dry run is successful, execute the playbook to apply the changes.

Phase 2: Gitea and Keycloak Deployment (Future)

Goal: Deploy Gitea on Mulder and Keycloak on Scully, along with their respective PostgreSQL databases.
Host and Role Assignments:
- Mulder: common, postgres, gitea
- Scully: common, postgres, keycloak (in addition to network)
Dependencies: This phase depends on the successful completion of Phase 1 and the availability of the domain name.
Next Steps: Once Phase 1 is complete, we will update the playbooks/main.yml and group_vars/all.yml to include the postgres, gitea, and keycloak roles.

3. What We Still Need

Your Domain Name: Please provide the domain name you want to use for your personal cloud (e.g., my-cloud.com). This is the last piece of information needed to proceed with the dry run for Phase 1.

4. Dry-Run

Before executing any changes, a dry run will be performed using the --check flag.

2.3 KiB Raw Blame History