Follow-up to FreeshardBase/freeshard#138 (inject shard-specific secrets into app compose templates).
Once #138 lands, document the secrets mechanism wherever compose-template variables / app_meta.json are described, so app authors know it exists:
- Syntax:
{{ secret.my-secret }} in an app's docker-compose template. Names are arbitrary; each distinct name yields one app-scoped secret.
- Generation: auto-generated on install, 32 chars from upper+lower+digits.
- Storage: persisted in the DB, scoped to shard + app.
- Lifecycle: kept across uninstall and upgrade (no rotation/regeneration for now).
- At rest: not encrypted (current scope).
Add a short copy-pasteable example app template using a generated secret (e.g. a DB password).
🤖 Generated with Claude Code
Follow-up to FreeshardBase/freeshard#138 (inject shard-specific secrets into app compose templates).
Once #138 lands, document the secrets mechanism wherever compose-template variables /
app_meta.jsonare described, so app authors know it exists:{{ secret.my-secret }}in an app's docker-compose template. Names are arbitrary; each distinct name yields one app-scoped secret.Add a short copy-pasteable example app template using a generated secret (e.g. a DB password).
🤖 Generated with Claude Code