void/system
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

ref(inventory): Split up inventory into group vars

Browse source 
One inventory targets a local machine (`inv-local.yaml`, chosen by default)
while the other targets a chrooted installation accessible from another
system, usually in the `/mnt/void` directory (`inv-chroot.yaml`, has to
be called like `ansible-playbook -i inv-chroot.yaml`).
This commit is contained in:
Marty Oehme 2025-03-02 08:49:48 +01:00
parent 19162e2af3
commit 030b8ec291
Signed by: Marty
GPG key ID: 4E535BC19C61886E
12 changed files with 399 additions and 265 deletions
Download patch file Download diff file Expand all files Collapse all files

19
README.md
View file

@ -1,7 +1,22 @@
# Install void linux from arch linux
Uses btrfs subvolumes, chroot and the void linux root tarball.
This is primarily made for _my_ setup to quickly get void linux up and running for playing around with stuff.
Uses btrfs subvolumes, chroot and the void linux root tarball for a full
installation. Can be used for a local system to keep it up-to-date and enable a
whole bunch of services for a full wayland workstation experience. This is
primarily made for _my_ setup to quickly get void linux up and running for
playing around with stuff.
## Usage
Currently the playbook defaults to keeping a 'local' system configured.
That means, you are running ansible on a void installation and it will operate on the local system itself.
To run like that just invoke `(sudo) ansible-playbook play.yaml`
or `(sudo) ansible-playbook play.yaml --tags=backup`
to run a specific tag.
To run a _full_ installation from an arch host system to a btrfs subvolume (through a void tarball)
run `(sudo) ansible-playbook -i inv-chroot.yaml play.yaml`, or a tagged version.
## Roadmap