1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
|
# CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
## Core Commands
**Install dependencies:**
```bash
ansible-galaxy install -r requirements.yml
```
**Run playbook:**
```bash
ansible-playbook site.yml --ask-become-pass
```
**Test connectivity:**
```bash
ansible all -m ping
```
**Run molecule testing:**
```bash
# Run full test suite for a specific scenario
molecule test -s archlinux
molecule test -s ubuntu
molecule test -s debian
molecule test -s raspberrypi
# Run specific test phases
molecule converge -s archlinux # Run converge only
molecule idempotence -s archlinux # Run idempotence test only
molecule verify -s archlinux # Run verify only
```
**Debug molecule testing on remote machine:**
```bash
# Copy to remote machine for debugging
rsync -r . archlinux.local:/opt/ansible-distro-configure
# Run on remote machine with proper PATH
ssh archlinux.local "cd /opt/ansible-distro-configure && PATH=~/.local/bin:\$PATH ~/.local/bin/molecule test -s archlinux"
```
## Architecture Overview
This is an Ansible configuration management repository for multiple Linux distributions
(Arch Linux, Ubuntu, Raspberry Pi).
The playbook configures systems with essential services, networking, user management, and security policies.
**Key Components:**
- `site.yml` - Main playbook with primary plays:
- "Distro bootstrap configure" (runs on all hosts): hostname, network, user, ssh, password_policy
- "Dev machines configure" (archlinux.local, ubuntu.local): locales, timezone, wireguard, homebrew, python, go, docker, podman
- "Raspberry Pi configure" (rpi5.local): locales, timezone, wireguard, gateway, pihole
- `inventory/hosts.yml` - Defines homelab hosts (archlinux.local, ubuntu.local, rpi5.local)
- `host_vars/` - Host-specific variables (encrypted with git-crypt)
- Contains network configuration, WireGuard VPN settings, user SSH keys
- Example files available for each supported distro
- `group_vars/all.yml` - Global variables (encrypted with git-crypt)
- User configuration, SSH settings, locale/timezone, password policies, Python versions
- `roles/` - Ansible roles for specific functionality:
- Core: hostname, network, user, ssh, password_policy
- System: locales, timezone, python, homebrew, docker, podman
- Network: wireguard, gateway, pihole
- Tools: ansible (multi-version management with pipx)
**Security & Encryption:**
- Host and group variables are encrypted using git-crypt
- SSH key-based authentication with configurable ports
- Password policies enforced via PAM
- WireGuard VPN configurations for secure networking
**Network Topology:**
The infrastructure uses a standard local network topology with direct router connectivity:
```
Internet
↕
Router (192.168.178.1)
↕
Local Network (192.168.178.0/24)
├── Raspberry Pi (192.168.178.254) ← Pi-hole DNS filtering
├── archlinux.local (192.168.178.201)
└── ubuntu.local (192.168.178.202)
```
**Traffic Flow:**
- **DNS Resolution**: All devices → Pi-hole (192.168.178.254) → Upstream DNS
- **Internet Traffic**: Local devices → Router → Internet (direct routing)
- **VPN Traffic** (when configured): Individual devices connect to external VPN servers
- **Container Registry Access**: Configured for Docker Hub via `/etc/containers/registries.conf`
**Raspberry Pi Services:**
- Pi-hole DNS filtering and ad blocking
- WireGuard VPN server capabilities (when `wireguard_gateway_enabled: true`)
- Standard network participant without NAT gateway functionality by default
**Gateway Role (Optional):**
The Pi can optionally act as a VPN gateway when `wireguard_gateway_enabled: true`:
- NAT masquerading for local subnet traffic through WireGuard tunnels
- IPv4/IPv6 traffic forwarding with configurable iptables rules
- Controlled by the `wireguard_gateway` role (disabled by default)
**Target Systems:**
- Development machines (Arch Linux, Ubuntu) - with development tools (Python, Go, Docker, Podman)
- Raspberry Pi infrastructure (Pi-hole DNS filtering, NAT gateway, WireGuard VPN)
- All systems configured via SSH with standard homelab naming (.local domains)
## Configuration Notes
- Configure SSH access in `~/.ssh/config` before running playbooks
- Copy and customize example files from `host_vars/*.yml.example` and `group_vars/all.yml.example`
- If not using git-crypt, remove `.gitattributes` and work with plaintext configs
- Requires community.general collection (`>=10.7.0, <11.0.0`)
## Coding Conventions
- Respect `.editorconfig`
- Respect linting rules (using `yamllint` and `ansible-lint`)
## CLI Rules
- Ask me to clarify if the prompt isn't clear enough
- If a task sounds wrong, please tell me so, and what are the best practices in that case
|
