aiolabs/omnixient
9
0
Fork 0
Code Issues 5 Pull requests Projects Releases Packages Wiki Activity Actions

docs: point template + install docs at the real Omnixient repo

Browse source 
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>
This commit is contained in:
Padreug 2026-06-28 11:45:27 +02:00
commit a31369fea8
4 changed files with 9 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

4
templates/default/README.md
View file

@ -1,6 +1,6 @@
# My Omnixient config
Generated from Omnixient's starter template (`nix flake init -t github:<your-org>/omnixient`).
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.
@ -32,7 +32,7 @@ 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 = "github:<your-org>/omnixient/v1.0.0"`.
`omni.url = "git+https://git.atitlan.io/aiolabs/omnixient?ref=v1.0.0"`.
## Secrets (optional)

2
templates/default/flake.nix
View file

@ -5,7 +5,7 @@
# Pin Omnixient. Point this at the canonical repo or your own fork, and
# ideally pin a release tag (…/omni/v1.0.0) for reproducible updates:
# nix flake update omni # pull the latest Omnixient, never touches your config
omni.url = "github:<your-org>/omnixient";
omni.url = "git+https://git.atitlan.io/aiolabs/omnixient";
# Reuse Omnixient's nixpkgs so you evaluate a single package set.
nixpkgs.follows = "omni/nixpkgs";
};