Compare commits
4 Commits
6f44aa7f76
...
feat/herme
| Author | SHA1 | Date | |
|---|---|---|---|
| fb16e2a259 | |||
| 6a2db08a58 | |||
| 670ae4f002 | |||
| f785abfd49 |
@@ -25,3 +25,12 @@ This document outlines the development conventions for this NixOS-based infrastr
|
||||
- **Secrets:** Secrets are managed with `agenix`. Edit encrypted files with `agenix -e <file>`.
|
||||
- **Modularity:** Structure configurations into logical, reusable modules under `modules/`. New modules should be registered in `modules/nixos/default.nix` to be available to all hosts.
|
||||
- **Error Handling:** Ensure Nix expressions are robust and handle potential evaluation errors gracefully.
|
||||
|
||||
## Workflow
|
||||
|
||||
- New feature → clean branch from `origin/master` → push → PR on Gitea
|
||||
- Branch naming: `feat/description` (features), `fix/description` (bugs/docs)
|
||||
- Always branch from `origin/master`, never from another feature branch
|
||||
- Submodule changes: commit submodule update in parent repo (the parent commit pins the submodule commit)
|
||||
- PR title should describe the change; body should explain motivation + summary
|
||||
- After PR merge, delete the feature branch
|
||||
|
||||
Submodule assets/compose updated: 611e96b306...1ec22ff3fc
Reference in New Issue
Block a user