void/system
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Ansible plays setting up the complete infrastructure of my voidlinux installation. Usable on local machine or through chroot.
59 commits 1 branch 0 tags 213 KiB
Shell 62.7%
Jinja 37.3%
Find a file
Marty Oehme afac310f21
ref(roles): All roles use desired package state 
By setting the `desired_package_state` variable we can change if ansible
should only ensure that the packages exist on the system (`present`) or
that they are also updated to their latest version (`latest`).
2025-03-13 11:24:14 +01:00
group_vars ref(inventory): Split up inventory into group vars 2025-03-13 11:24:13 +01:00
roles ref(roles): All roles use desired package state 2025-03-13 11:24:14 +01:00
.gitignore ref(inventory): Split up inventory into group vars 2025-03-13 11:24:13 +01:00
ansible.cfg ref(inventory): Split up inventory into group vars 2025-03-13 11:24:13 +01:00
inv-chroot.yaml ref(inventory): Split up inventory into group vars 2025-03-13 11:24:13 +01:00
inv-local.yaml ref(inventory): Split up inventory into group vars 2025-03-13 11:24:13 +01:00
play.yaml ref(playbook): Change to role-based structure 2025-03-13 11:24:08 +01:00
README.md ref(inventory): Split up inventory into group vars 2025-03-13 11:24:13 +01:00
requirements.yaml Set up basic ansible repo 2025-02-21 17:57:58 +01:00

README.md

Install void linux from arch linux

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

  • printing

  • audio

  • arduino/iot

  • vpn

  • statusbar integration

  • custom repository

  • automatic kernel rebuild

    • should try to update kernel first (if desired_state == latest)
    • if changed should hook into booster kernel rebuild
    • then delete last kernel?

  • automatic kernel boot selection

    • refind should either manually be pointed to correct kernel(s)
    • or kernel/initramfs/config should be renamed to simple items
      • could maybe symlink to booster-void.img and initramfs-void.img?
      • and then do a search and add subitems for each 6.12.xyz kernel found?

Package wishlist

packages to build xbps-src style: - [x] filtile (src) - [x] dotter (src) - [x] git-bug (src) - [ ] bemoji! - [~] git-delta - [ ] bugwarrior - [ ] viddy - [ ] netbird

  • wifi setup
    • impala (iwd TUI)