feat(gitops): auto-deploy asus when its config changes on main #22
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
polen/nixos!22
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/asus-gitops-deploy"
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?
Same one-shot root pattern as the server: the runner SSHes
forgejo-deploy@asusand startsnixos-deploy.service, which pullsmainand runsnixos-rebuild switch --flake ref=main#asus.services.nixos-deploy(ref=main#asus, ntfyhomelab), dedicatedforgejo-deploySSH user (polkit-restricted to the unit)asus_deploy_keyreadable by the runnerdeploy-asus.yml(push to main, pathsdevices/asus/**),build-asusjob in check.ymlREQUIRES before merge: add
deploy_ssh_key:tosecrets/secrets.yamlwith the private key at~/workspace/tmp/asus_deploy_key(viasops). The asus sops manifest build intentionally fails until then — thebuild-asusjob being red is the guard working.Order: merge #21 (monerod) first, then add the secret, then merge this one.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.