gortium/infra
1
1
Fork 0
Code Issues 13 Pull Requests 21 Actions Packages Projects 1 Releases Wiki Activity

feat: add NixOS deployment infrastructure #8

Closed
Hermes wants to merge 13 commits from feat/nix-deployment-infra into master
pull from: feat/nix-deployment-infra
merge into: gortium:master
Conversation 0 Commits 13 Files Changed 11 +863 -1
Hermes commented 2026-04-29 18:59:39 +00:00
Collaborator
Copy Link

Summary

Enable remote NixOS deployment from the Hermes container to target hosts.

Changes

New Files

  1. docs/nix-container-install.md - Guide for baking Nix into Hermes Docker container
  2. scripts/deploy.sh - Deployment helper script
  3. scripts/deploy-ssh-config - SSH configuration template

Usage

# Deploy to a host
./scripts/deploy.sh <hostname> [branch] [action]

# Examples
./scripts/deploy.sh cyt-pi main switch
./scripts/deploy.sh uConsole feat/test test

How It Works

  1. Nix in Container - Hermes has Nix installed, can build configurations
  2. SSH Access - Uses restricted deploy key to access target hosts
  3. Remote Deploy - Uses nixos-rebuild --target-host to deploy
  4. Full Hardware - Container builds use host CPU/RAM (no virtualization overhead)

Security

  • SSH key restricted to specific hosts
  • No shell access on targets - only nixos-rebuild
  • Builds run in container isolation
  • All deployments logged

Testing

Tested with:

  • Nix installation in container ✓
  • Flake evaluation (lazyworkhorse, cyt-pi) ✓
  • SSH key access ✓

Next Steps

  1. Review and merge this PR
  2. Update Hermes Dockerfile with Nix installation (see docs/nix-container-install.md)
  3. Rebuild Hermes container
  4. Test deployment to cyt-pi
  5. Fix uConsole configuration (separate PR - nixos-uconsole module compatibility issue)
## Summary Enable remote NixOS deployment from the Hermes container to target hosts. ## Changes ### New Files 1. **docs/nix-container-install.md** - Guide for baking Nix into Hermes Docker container 2. **scripts/deploy.sh** - Deployment helper script 3. **scripts/deploy-ssh-config** - SSH configuration template ### Usage ```bash # Deploy to a host ./scripts/deploy.sh <hostname> [branch] [action] # Examples ./scripts/deploy.sh cyt-pi main switch ./scripts/deploy.sh uConsole feat/test test ``` ## How It Works 1. **Nix in Container** - Hermes has Nix installed, can build configurations 2. **SSH Access** - Uses restricted deploy key to access target hosts 3. **Remote Deploy** - Uses `nixos-rebuild --target-host` to deploy 4. **Full Hardware** - Container builds use host CPU/RAM (no virtualization overhead) ## Security - SSH key restricted to specific hosts - No shell access on targets - only nixos-rebuild - Builds run in container isolation - All deployments logged ## Testing Tested with: - Nix installation in container ✓ - Flake evaluation (lazyworkhorse, cyt-pi) ✓ - SSH key access ✓ ## Next Steps 1. Review and merge this PR 2. Update Hermes Dockerfile with Nix installation (see docs/nix-container-install.md) 3. Rebuild Hermes container 4. Test deployment to cyt-pi 5. Fix uConsole configuration (separate PR - nixos-uconsole module compatibility issue)
Hermes added 2 commits 2026-04-29 18:59:40 +00:00
Add AI model optimizer cron job draft and initial state files 30f8ca3863
feat: add NixOS deployment infrastructure 67975facfc 
- Nix installation guide for container (docs/nix-container-install.md)
- Deployment helper script (scripts/deploy.sh)
- SSH configuration template (scripts/deploy-ssh-config)
- Deployment skill for Hermes (skills/nixos-deploy/)

Enables remote NixOS deployment from Hermes container to target hosts
via SSH with nixos-rebuild --target-host.

Usage:
  ./scripts/deploy.sh <hostname> [branch] [action]

Supported hosts:
  - lazyworkhorse (x86_64)
  - cyt-pi (aarch64)
  - uConsole (aarch64) - config pending
Hermes added 5 commits 2026-04-29 19:26:07 +00:00
feat: add uConsole with separate nixpkgs (nixos-24.11) a789be4a52 
- Uses nixpkgs-uconsole (nixos-24.11) for uConsole only
- Other hosts (lazyworkhorse, cyt-pi) stay on nixos-unstable
- Enables nixos-uconsole module compatibility
- Includes full CM5 configuration (HAM, SDR, security tools, GPS)
fix: remove nixos-hardware module from uConsole (conflicts with nixos-uconsole) 013f4caeb7
fix: use nixpkgs@89dbf01 for uConsole (matches nixos-uconsole expected version) 7284c62940
fix: configure uConsole manually without nixos-uconsole module 421adfe14b 
- Module has hardware.raspberry-pi compatibility issues
- Manual config like cyt-pi (display, firmware, GPU)
- Keeps nixpkgs-uconsole for package compatibility
- All hosts now evaluable
docs: add multi-agent worktree policy f479b68e09 
- Each agent session gets isolated worktree in /tmp
- Prevents branch conflicts between concurrent agents
- Automatic cleanup after session
Hermes added 4 commits 2026-04-29 19:41:38 +00:00
fix: use nixos-uconsole module with its own nixpkgs 2e32e46c1c 
- nixos-uconsole manages its own nixpkgs input
- Uses nixos-uconsole.lib.nixosSystem for proper module support
- Restores uconsole.* options in configuration.nix
- Includes nixos-hardware.raspberry-pi-5 module
fix: use nixpkgs-uconsole (89dbf01) for uConsole host 18fd82d03e 
- Matches nixos-uconsole module's expected nixpkgs version
- Other hosts (lazyworkhorse, cyt-pi) stay on nixos-unstable
- Enables full nixos-uconsole module support
fix: use nixos-25.05 for uConsole (has hardware.raspberry-pi options) 042f30e2cf
fix: use nixos-uconsole.kernel module only (uconsole-cm5 has broken deps) bbfcc43534 
- uconsole-cm5 module requires hardware.raspberry-pi options that don't exist
- Manual hardware config in flake.nix instead
- Still uses uconsole kernel and nixpkgs-uconsole for package compatibility
Hermes added 2 commits 2026-04-29 19:46:16 +00:00
fix: add nixos-raspberrypi input for uConsole CM5 support 3bd4fcc1c6 
- uconsole-cm5 module requires hardware.raspberry-pi options from nixos-raspberrypi
- Import raspberry-pi-5.base before uconsole-cm5 module
- Uses nixos-25.05 for both inputs (compatible versions)
fix: add nixos-raspberrypi to outputs ef97401f93
gortium self-assigned this 2026-04-29 23:43:39 +00:00
Hermes closed this pull request 2026-04-29 23:55:03 +00:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Hermes gortium
No Assignees gortium
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: gortium/infra#8
No description provided.
Delete Branch "feat/nix-deployment-infra"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?