No description
- Nix 75.6%
- Python 17.4%
- TypeScript 6.8%
- Just 0.2%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
| .zed | ||
| claude | ||
| modules | ||
| secrets | ||
| .envrc | ||
| .gitignore | ||
| .mcp.json | ||
| .sops.yaml | ||
| CLAUDE.md | ||
| flake.lock | ||
| flake.nix | ||
| globals.nix | ||
| Justfile | ||
| lamp-ble-proxy.yaml | ||
| m5stack-atom-echo-1b4530.yaml | ||
| README.md | ||
nixos-configs
NixOS configurations for the machines I manage.
Currently managed systems:
- blocktech: My current laptop, a ThinkPad P1 running GNOME.
- gamepc: My gaming PC running Cosmic
- warwick: A Raspberry Pi 4 Model B, which mostly does monitoring
- atlas: A Gigabyte Brix, currently running NixOS containers
- lewis: A Gigabyte Brix, currently running NixOS containers
- roeland: A Minisforum UN100P, runs my Jellyfin + *arr + Audiobookshelf setup
Deployment
I use Colmena for deploying my machines.
To apply to the local machine:
sudo colmena apply-local --sudo
To apply to all remotely managed systems:
colmena apply
Collabora manual actions
Apart from the declarative commands, these commands also need to be ran on the server for a successful Collabora setup:
# From the perspective of Nextcloud
nextcloud-occ config:app:set richdocuments wopi_url --value="http://collabora.mesh.kun.is:9980"
# From the perspective of clients
nextcloud-occ config:app:set richdocuments public_wopi_url --value="http://collabora.mesh.kun.is"
nextcloud-occ richdocuments:activate-config