homelab-apps

Architecture Decision Records following Nygard's lightweight template

Design patterns for authentication, routing, error handling, and forms

Architectural conventions and decision-making guidelines

Code style, patterns, and implementation conventions

Conventional Commits specification for structured commit messages

How to start a development server in the background and construct the public URL for port-forwarding in this homelab environment

Automate browser interactions, test web pages and work with Playwright tests.

Conventions and tooling to expect when starting a new project

Testing strategy, patterns, and execution conventions

Wire application secrets from Pulumi ESC into an app in homelab-apps using the External Secrets Operator. Use when the user says "this app needs an API key", "add a secret to this app", "configure credentials for this service", or "pull a secret from ESC into the app".

Add a new personal app to the homelab-apps monorepo and deploy it to the homelab k3s cluster via GitHub Actions CI/CD. Use when the user wants to self-host a new application (e.g. Vaultwarden, Gitea, Jellyfin) on their homelab cluster using the homelab-apps pattern.

Add a PostgreSQL database (via CloudNativePG) to an app in homelab-apps. Use when the user wants to deploy an app that needs a database, e.g. "this app needs postgres", "add a DB to this app", "deploy with persistent SQL storage".

Add GitHub OAuth authentication (via the centralized oauth2-proxy) to an app in homelab-apps. Use when the user says "protect this app with auth", "add login to this app", "require GitHub sign-in", or "only I should be able to access this app".