Repository Strategy
Target Repositories
Section titled “Target Repositories”| Repository | Responsibility | Visibility |
|---|---|---|
weather-app |
Application code, tests, Dockerfiles, Helm chart and application SBOMs | Public mirror when safe |
homelab-platform |
Platform substrate, OPNsense, Kubernetes, Argo CD, observability and GOAD automation | Private by default |
gitlab-ci-templates |
Reusable GitLab CI components and templates | Public or internal mirror |
portfolio-docs |
Documentation-as-code site | Public |
Implementation Choice
Section titled “Implementation Choice”Each project has its own lifecycle, CI/CD contract and visibility boundary. The projects are kept logically separate even when local workspaces colocate them for cross-repository implementation.
Publishing Direction
Section titled “Publishing Direction”GitHub Pages is the default publishing target because the documentation is static and easy to share. GitLab remains the primary CI/CD platform. A mirror from GitLab to GitHub keeps delivery and publication responsibilities separated.