jordan 1e853980e4 feat: inject provisioned credentials into component deployments

Components now automatically receive DATABASE_URL, REDIS_URL, and other
infrastructure credentials when deployed. Previously, credentials were
provisioned and stored but never injected into K8s deployments.

Changes:
- Add fetchProjectCredentials() to component_deploy.go
- Populate spec.Secrets before calling deployer.Deploy()
- Fix slackpath-4 to provision postgres + redis before services
- Add terminology docs to clarify platform vs skeleton code

This completes the infrastructure provisioning flow:
1. add-db → provisions CockroachDB, stores DATABASE_URL
2. add-service → deploys with DATABASE_URL in environment

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-02-05 00:09:15 -07:00

1.4 KiB

Raw Blame History

rdev Terminology

Last Updated: 2026-02-05 Confidence: High

Summary

Distinguishing between rdev code (the platform) and generated project code (skeleton) prevents confusion when discussing implementations.

Core Terms

Term	Definition	Code Location
platform	rdev API itself—handlers, services, adapters, workers	`cmd/rdev-api/`, `internal/`, `pkg/api/`
skeleton	Monorepo base that ships in every generated project	`templates/skeleton/`
component templates	Templates for services, workers, apps, CLIs added to skeleton	`templates/components/`
generated project	A project created by rdev (contains skeleton + components)	Lives in Gitea repos

Usage Examples

"Add auth middleware to platform" → edit internal/auth/
"Add auth middleware to skeleton" → edit templates/skeleton/pkg/auth/
"Platform's work queue" → internal/adapter/postgres/work_queue.go
"Skeleton's job queue" → templates/skeleton/pkg/queue/ (planned)

File Pointers

Platform entry: cmd/rdev-api/main.go
Skeleton root: internal/adapter/templates/templates/skeleton/
Component registry: internal/adapter/templates/registry.go

Composable Monorepo - Skeleton + component architecture
Template Provider - How templates are seeded

1.4 KiB Raw Blame History