aiolabs/omnixient
9
0
Fork 0
Code Issues 5 Pull requests Projects Releases Packages Wiki Activity Actions
omnixient/templates/default/README.md
Padreug a31369fea8 docs: point template + install docs at the real Omnixient repo 
Replace the <your-org> placeholders with the actual public URL
(git+https://git.atitlan.io/aiolabs/omnixient, https so forkers need no
SSH), and switch the packs standalone-import example from git+ssh to the
same https URL.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-28 11:45:27 +02:00

1.5 KiB
Raw Permalink Blame History

My Omnixient config

Generated from Omnixient's starter template (nix flake init -t git+https://git.atitlan.io/aiolabs/omnixient). You consume Omnixient as a flake input — you do not fork it — so nix flake update omni pulls upstream changes without ever touching your files.

Setup

  1. Edit flake.nix — set the omni.url to the real repo, and fill in the settings block (user, hostName, timeZone, theme, stateVersion).
  2. Generate your hardware scan: 
    sudo nixos-generate-config --show-hardware-config \
  > hosts/myhost/hardware-configuration.nix
    (Rename hosts/myhost to your hostname if you like; keep flake.nix in sync.)
  3. Pick packs / options in hosts/myhost/default.nix.
  4. git add everything — flakes only see git-tracked files.
  5. Build & switch (first build on a flakes-disabled system needs the flag): 
    sudo nixos-rebuild switch --flake .#myhost \
  --extra-experimental-features "nix-command flakes"

Updating

nix flake update omni   # pull latest Omnixient (a pinned dependency)
sudo nixos-rebuild switch --flake .#myhost

This can't conflict with your config — Omnixient is an input, not a checkout. Roll back by reverting flake.lock. Pin a release with omni.url = "git+https://git.atitlan.io/aiolabs/omnixient?ref=v1.0.0".

Secrets (optional)

Off by default. To enable, set omni.secrets.enable = true and provide your own age key + secrets/omni.yaml — see Omnixient's docs/getting-started.md.