Files
sor/deploy/secrets/README.md
T
9186a2a7f3 Hide sidebar until authenticated; wire Admin seed credentials
- MainLayout.razor: wrap shell in <AuthorizeView> so the sidebar and
  nav are only rendered when the user is logged in. Unauthenticated
  pages (login) render @Body directly, giving the login card its full
  viewport without the nav overlay.
- deployment-admin.yaml: inject Admin__Email / Admin__Password from
  sor-app-secrets so the startup seed picks up production credentials.
- sor-app-secrets.yaml.template: add Admin__Email / Admin__Password
  placeholder entries with instructions.
- secrets/README.md: document the two new seed-account keys.

Generated with [Claude Code](https://claude.ai/code)
via [Happy](https://happy.engineering)

Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Happy <yesreply@happy.engineering>
2026-02-27 09:47:20 -05:00

65 lines
3.0 KiB
Markdown

# SOR Kubernetes Secrets
These files are **NOT committed to git** (excluded via root `.gitignore`).
The `*.yaml.template` files in this directory ARE committed — copy them, fill in
real values, then apply to the cluster.
---
## Quick Setup
### 1. Harbor image pull secret
```bash
cp harbor-pull-secret.yaml.template harbor-pull-secret.yaml
# edit harbor-pull-secret.yaml — fill in your Harbor username and password
kubectl apply -f harbor-pull-secret.yaml
```
### 2. Application secrets
```bash
cp sor-app-secrets.yaml.template sor-app-secrets.yaml
# edit sor-app-secrets.yaml — fill in Postgres connection string and CDN credentials
kubectl apply -f sor-app-secrets.yaml
```
### 3. Gitea Actions repository secrets
In your Gitea repository → Settings → Secrets, add:
| Name | Value |
|-------------------|--------------------------------|
| HARBOR_USERNAME | Your Harbor robot account name |
| HARBOR_PASSWORD | Your Harbor robot account token |
---
## Secrets Reference
| Secret Name | Key | Used By | Notes |
|--------------------|----------------------------|-----------------|-------------------------------------------------|
| sor-app-secrets | ConnectionStrings__Default | host + admin | Postgres connection string |
| sor-app-secrets | Admin__Email | admin only | Seed SuperAdmin email (default: admin@sor.local) |
| sor-app-secrets | Admin__Password | admin only | Seed SuperAdmin password (12+ chars required) |
| sor-app-secrets | Cdn__PublicBaseUrl | host + admin | e.g. https://cdn.aeternalisgames.com |
| sor-app-secrets | Cdn__EndpointUrl | host + admin | Ceph RadosGW endpoint, e.g. http://172.10.1.60:7480 |
| sor-app-secrets | Cdn__AccessKey | host + admin | S3 access key ID |
| sor-app-secrets | Cdn__SecretKey | host + admin | S3 secret access key |
| sor-app-secrets | Cdn__BucketName | host + admin | S3 bucket name, e.g. sor-assets |
| redis-credentials | connection-string | host only | **Already exists** in stone-server ns |
| harbor-credentials | .dockerconfigjson | both pods | Harbor image pull secret |
---
## Notes
- `redis-credentials` is assumed to already exist in the `stone-server` namespace.
If the key name inside it is different from `connection-string`, update
`deploy/k8s/deployment-host.yaml` to match.
- The Redis connection string format expected by StackExchange.Redis:
`HOST:PORT,password=PASSWORD,ssl=true,abortConnect=false`
- The Postgres connection string format expected by Npgsql:
`Host=HOST;Port=5432;Database=SOR;Username=USER;Password=PASSWORD;`
- For production, consider enabling SSL on the Postgres connection:
`...;SSL Mode=Require;Trust Server Certificate=true`