d168115f81
ref(acpi): Spin out acpi role
2025-03-13 11:24:16 +01:00
b3b280fbe4
ref(playbook): Change to role-based structure
2025-03-13 11:24:08 +01:00
8e79c5f804
ref(playbook): Move all plays into separate directory
2025-02-23 11:39:24 +01:00
996560410e
ref(inventory): Make chroot target one child of target systems
...
This should allow just having a general 'target' system for ansible
which will take all the modifications - but not care whether we connect
to it locally (i.e. running from void) or through chroot.
We can set the connection method for the specific system(s) in whatever
we group as part of the target group then. For local installation we
simply add locally connected hosts and for chroot set up chrooted hosts.
2025-02-23 11:39:24 +01:00
9775627854
ref(packages): Rename from custom to packages
2025-02-23 11:39:19 +01:00
e70b6428fd
ref(inventory): Rename guest group to void
2025-02-23 11:39:18 +01:00
6aa2188f50
feat(wayland): Add wayland stack
2025-02-23 10:12:35 +01:00
c321289ca0
feat(custom): Add keyd service
2025-02-23 10:12:33 +01:00
457fb3517a
feat(network): Create separate networking playbook
2025-02-23 10:12:31 +01:00
f77a5c4e33
ref(base): Rename guest playbook to void_base
...
Sets up the void basics while other playbooks handle other things
2025-02-23 10:12:31 +01:00
a3df7eeb27
feat(user): Set up user management for void
2025-02-21 17:58:07 +01:00
8a77b201bd
Split up playbooks into host-level and guest-level
2025-02-21 17:58:03 +01:00
bf1e99b197
Create rootfs for mounted void guest
2025-02-21 17:58:03 +01:00
45f9d88890
Install system through chroot
2025-02-21 17:58:02 +01:00
9c06b98fde
Set up basic ansible repo
2025-02-21 17:57:58 +01:00
