| Age | Commit message (Collapse) | Author |
|---|
|
- Add Omni/Deploy/ with Manifest, Deployer, Systemd, Caddy modules
- Manifest CLI: show, update, add-service, list, rollback commands
- Deployer: polls S3 manifest, pulls closures, manages systemd units
- Caddy integration for dynamic reverse proxy routes
- bild: auto-cache to S3, outputs STORE_PATH for push.sh
- push.sh: supports both NixOS and service deploys
- Biz.nix: simplified to base OS + deployer only
- Services (podcastitlater-web/worker) now deployer-managed
- Documentation: README.md with operations guide
|
|
When I deploy, I get an error like this:
Error: Failed to open dbus connection
Caused by: Failed to connect to socket /run/user/1000/bus:
Connection refused
According to Claude, this is because dbus is trying to do stuff while
I'm running the `systemd-run` command, but that loses my user context so
dbus errors out, and I can disable dbus by setting this variable to
nothing. I guess we'll see if it works!
|
|
This guards against network failures that may put the system in an unusable
state. It's included in nixos-rebuild, so I should include it here in some form
too.
https://github.com/NixOS/nixpkgs/pull/258571
|
|
Supposedly, running the nix-env command before switch-to-configuration will
result in the grub entry being updated appropriately, and this is how
nixos-rebuild does it.
https://discourse.nixos.org/t/how-to-update-grub-entries-with-nixos-config-built-with-nix-build/1826/2
|
|
I was getting confused about what is a product and what is internal
infrastructure; I think it is good to keep those things separate. So I moved a
bunch of stuff to an Omni namespace, actually most stuff went there. Only things
that are explicitly external products are still in the Biz namespace.
|
