infra/README.md

Infra — Personal Infrastructure as Code

Italian version: README.it.md

This is my Ansible repo for keeping my personal machines and dotfiles in sync. It is the source of truth for packages, services, and user configuration. The setup is meant to stay modular, reproducible, and idempotent without getting too clever.

Layout

infra/
├── ansible/
│   ├── site.yml
│   ├── inventory/
│   │   ├── hosts.yml
│   │   ├── group_vars/
│   │   └── host_vars/
│   ├── templates/
│   └── roles/
├── dotfiles/
│   ├── common/
│   ├── desktop/
│   ├── fedora/
│   ├── ubuntu/
│   ├── server/
│   ├── workstation/
│   ├── workstation_dev_wsl/
│   └── nymph/
├── scripts/
├── secrets/
├── README.md
└── README.it.md

• ansible/ holds provisioning and host configuration.
• dotfiles/ holds versioned user configuration.

Managed machines

The repo currently covers Fedora/GNOME desktops, one Fedora WSL workstation, and an Ubuntu server. Configuration is layered instead of being tied to host names:

common user environment
+ platform-specific setup
+ role-specific software
+ independently selected desktop
+ host overrides

Host	Platform	Role	Desktop
ikaros	Fedora	Personal workstation	GNOME
nymph	Fedora	Desktop laptop	GNOME
deadalus	Fedora WSL	Development workstation	—
prometheus	Ubuntu	Server	—

ikaros must be boring
nymph is allowed to break

ikaros is the stable personal Fedora/GNOME desktop. nymph is the laptop and gets the same shared desktop dotfiles while GNOME itself stays close to the Fedora defaults. The legacy void and desktop groups are compatibility parents; the main axes are platform_*, role_*, and desktop_*.

Desktop profiles

• ikaros: stable Fedora Workstation + GNOME desktop.
• nymph: Fedora Workstation + GNOME laptop.
• Void desktops stay available as reusable future profiles through platform_void + graphical_desktop.

Void uses desktop_environment: minimal. Sway is the normal session; add a host to desktop_niri to select Niri. GNOME is only handled on Fedora through desktop_gnome.

The desktop setup includes shared desktop dotfiles, Sway/Niri support for future Void hosts, emptty, turnstile user services, a stable ssh-agent socket at ~/.local/state/ssh-agent/socket, Emacs authoring config, tmux bootstrapped through TPM, Flatpak, GNOME Keyring, Udiskie, and kanshi for Sway multi-monitor setups.

Void package buckets stay separate on purpose:

• void_packages_base: system runtime and services.
• desktop_common_packages: shared GUI infrastructure.
• desktop_minimal_packages: GTK applications and emptty.
• desktop_sway_packages: Sway-only binaries.

Workstation

deadalus is the only workstation target. It is Fedora running in WSL on the Windows machine with the same name. Flatpak and Snap are explicitly kept out of this profile.

The workstation receives two layers:

• Fedora development setup through workstation_dev_fedora.
• WSL setup with systemd through workstation_dev_wsl.

That gives it Fedora packages through DNF, Docker from the official repository, shared workstation dotfiles and templates, tmux helpers, and WSL systemd configuration. Windows applications are installed manually; the WSL profile does not manage Python remoting components for them.

WSL workflow

1. Start Fedora WSL once and finish creating the Linux user.
2. Install Ansible inside Fedora WSL.
3. Run the playbook from that distribution with --limit deadalus.
4. Use Windows-side VS Code with Remote WSL, Remote SSH, and Dev Containers if wanted.

Server

prometheus is the Ubuntu LTS server. It has no graphical environment and gets server-specific dotfiles and templates.

The server profile installs Ubuntu packages, Docker from the official repository, declared systemd services, UFW rules, and the server Compose stack. Syncthing ports 22000/tcp, 22000/udp, and 21027/udp are opened; the Syncthing GUI is not directly opened in UFW.

Server identity comes from server_username, server_user_group, and server_user_home in ansible/inventory/group_vars/server.yml. server_username defaults to username, but it can be overridden, for example:

ansible-playbook ansible/site.yml --limit prometheus -e server_username=myuser
ansible-playbook ansible/site.yml --limit prometheus \
  -e server_username=myuser -e server_user_group=mygroup \
  -e server_user_home=/srv/myuser

How layering works

A host can intentionally belong to more than one inventory group. The final configuration is the combination of the host and its groups, not a one-host/one-play mapping.

common configuration
+ platform configuration
+ role configuration
+ desktop configuration
+ host overrides

Current examples:

ikaros   -> common + platform_fedora + role_personal_workstation + graphical_desktop + desktop_gnome + ikaros
nymph    -> common + platform_fedora + graphical_desktop + desktop_gnome + nymph
deadalus -> common + platform_fedora + workstation_dev_fedora + workstation_dev_wsl + deadalus

This keeps shared configuration reusable, lets host overrides stay small, and leaves the Void desktop profile ready for a future host using platform_void + graphical_desktop + desktop_sway.

Emacs is enabled on Fedora/GNOME and workstation profiles. dotfiles_common deploys the canonical authoring setup, including ~/Org/, versioned templates, and PDF/HTML/Markdown/DOCX/ODT export support. To turn it on temporarily elsewhere:

ansible-playbook ansible/site.yml --limit <host> --tags emacs -e emacs_enabled=true

Main roles

Role	What it does
packages_void	Installs packages on Void.
packages_freebsd	Installs packages on FreeBSD with pkg.
packages_ubuntu	Installs packages on Ubuntu.
packages_fedora	Installs packages on Fedora.
services_runit	Manages runit services.
services_systemd	Manages systemd services.
services_freebsd	Manages declared FreeBSD rc services.
profile_desktop_common	Shared Void desktop bootstrap.
profile_desktop_gnome	Shared Fedora/GNOME desktop dotfiles.
profile_desktop_sway	Sway / SwayFX Wayland session.
profile_desktop_niri	Niri Wayland session on Void.
profile_desktop_host	Host-specific desktop overrides.
profile_personal_workstation	Stable personal-workstation layer.
profile_workstation_dev_common	Shared workstation development setup.
profile_workstation_dev_wsl	WSL development setup.
profile_server	Server setup.
dotfiles_common	Shared user dotfiles.

What site.yml runs

all -> dotfiles_common
platform_void -> packages_void + services_runit
platform_void & graphical_desktop -> profile_desktop_common + profile_desktop_sway + profile_desktop_niri + profile_desktop_host
platform_freebsd -> packages_freebsd + services_freebsd
platform_fedora -> packages_fedora + services_systemd
platform_fedora & role_personal_workstation -> profile_personal_workstation
platform_fedora & desktop_gnome -> profile_desktop_gnome
workstation_dev_fedora -> profile_workstation_dev_common
workstation_dev_wsl -> profile_workstation_dev_wsl (after platform_fedora + workstation_dev_fedora)
ubuntu_server -> packages_ubuntu + services_systemd + profile_server

So, in practice:

• platform_fedora configures ikaros, nymph, and deadalus.
• deadalus gets the Fedora development layer followed by the WSL layer.
• ubuntu_server configures prometheus.
• Empty platform_void and platform_freebsd groups do nothing until they get a host.
• The playbook never restarts the display manager during a run.
• secrets/vault.yml and then secrets/vault.local.yml are loaded only when present.

Requirements

You will need Python 3, Ansible, ansible-lint, yamllint, shellcheck, and the collections in ansible/collections/requirements.yml.

python3 -m pip install ansible ansible-lint yamllint shellcheck-py
ansible-galaxy collection install -r ansible/collections/requirements.yml

Secrets are optional:

• secrets/vault.yml can hold shared local vault values.
• secrets/vault.local.yml can hold untracked local overrides.
• secrets/vault.yml.example is the example template.
• If no vault file exists, the playbook still runs without those optional values.
• secrets/.vault_pass.gpg is used when available; secrets/.vault_pass is a legacy local fallback. Without either one, Ansible asks for the password interactively.

Running it

Run the whole playbook:

ansible-playbook ansible/site.yml

Useful checks before applying changes:

ansible-playbook ansible/site.yml --syntax-check
ansible-playbook ansible/site.yml --limit ikaros,nymph --check --diff
ansible-playbook ansible/site.yml --limit ikaros --check --diff
ansible-playbook ansible/site.yml --limit nymph --check --diff
ansible-playbook ansible/site.yml --limit deadalus --check --diff
ansible-playbook ansible/site.yml --limit prometheus --check --diff
ansible-lint ansible/site.yml
ansible-lint ansible/roles
yamllint ansible/

For focused checks:

ansible-playbook ansible/site.yml --limit <host> --tags <tag1>,<tag2> --check --diff
ansible-playbook ansible/site.yml --limit <host> --start-at-task "<task name>" --check --diff
ansible-lint ansible/roles/<role>
yamllint ansible/path/to/file.yml
docker compose -f /opt/docker/server/docker-compose.yml config

Tags

Use Ansible as the source of truth for the current tag list:

ansible-playbook ansible/site.yml --list-tags

Tag	Main scope
always	Common pre-tasks, including optional vault loading.
ai_agents	Shared AI agent installation on Fedora and WSL.
dotfiles	User configuration across all profiles.
dotfiles:common	Shared dotfiles.
dotfiles:desktop	Void and Fedora/GNOME desktop dotfiles.
dotfiles:host	Host-specific Void desktop overrides.
dotfiles:server	Server dotfiles.
dotfiles:workstation	Personal workstation and WSL dotfiles.
emacs	Shared Emacs setup and authoring dependencies.
gnome	Fedora/GNOME desktop configuration.
npm	Global npm packages.
packages	Package installation and updates.
services	runit and systemd services.
tmux	tmux configuration and plugins.
wsl	WSL bootstrap and configuration.

Bootstrapping a new machine

git clone <repo>
cd <repo-dir>
ansible-galaxy collection install -r ansible/collections/requirements.yml
ansible-playbook ansible/site.yml

For a future Void desktop host:

1. Add it to platform_void.
2. Add it to graphical_desktop.
3. Use Sway, or add it to desktop_niri for Niri.
4. Put hardware-specific details in host_vars/<host>.yml.

The legacy void and desktop groups remain compatibility parents, so hosts in platform_void and graphical_desktop still receive the existing Void and desktop variables.