docs: integrate RDS and ACK architecture memory

This commit is contained in:
brother7 committed 2026-08-12 19:20:07 +08:00
1 parent c44274f098
commit bb004f02b3
8 files changed
+97 -19

No files matched your search

+13 -9
View File
@@ -4,33 +4,37 @@ This file is the integrated default-branch snapshot. Feature tasks record progre
## Integrated Through
- {source task or merge commit}
- `84d84ba94f136f10624700e8d34ed19fc6fe7fe7` (`20260812-rds-postgres-adapter-7f2c1a`)
## Current Focus
The project is currently focused on {current focus}.
The application now has a production deployment path for Alibaba Cloud ACK backed by direct Alibaba Cloud RDS PostgreSQL access. Local JSON remains an explicit development/test backend.
## Recently Completed
- {YYYY-MM-DD}: {completed work summary}
- 2026-08-12: Replaced the Supabase/PostgREST runtime path with a server-only `pg` adapter across data, account, and billing stores.
- 2026-08-12: Added versioned PostgreSQL migrations, strict backend selection, verified-CA TLS, database readiness, and ACK Web/Worker/migration manifests.
## In Progress
- {in-progress item}
- Production environment values and the real RDS/ACK rollout are not yet validated in this repository environment.
## Next Recommended Steps
1. {next recommended step}
2. {next recommended step}
1. Back up the target database; create separate migration and application roles; verify the RDS internal endpoint, VPC connectivity, whitelist, TLS mode, and CA certificate.
2. Build and push the reviewed image, run the one-shot migration Job, confirm `/api/ready`, then roll out Web and Worker.
3. Keep Web at one replica until generated assets are externalized to OSS or another shared object store.
## Open Questions / Blockers
- {open question or blocker}
- Target RDS PostgreSQL version, connection budget, endpoint, TLS enforcement, CA bundle, database roles, and ACK network policy remain deployment inputs.
## Risky Areas
- {risky area}
- Database migrations and least-privilege grants must be tested against the actual RDS instance before production cutover.
- Web pods still own runtime files; PostgreSQL does not make local uploads/generated assets safe for horizontal Web scaling.
- The current image runs as root; moving to a non-root user requires an explicit writable-path ownership design.
## Last Updated
{YYYY-MM-DD}
2026-08-12
+1
View File
@@ -4,6 +4,7 @@
| Date | Task | Outcome | Docs Updated |
|---|---|---|---|
| 2026-08-12 | `20260812-rds-postgres-adapter-7f2c1a` | Direct PostgreSQL/RDS persistence and ACK deployment support integrated; local JSON retained for development/tests. | Current state, architecture, data flow, module map, decisions, commitments |
## Notes
@@ -0,0 +1,41 @@
# Task: Integrate RDS PostgreSQL support into main
## Identity
- Task ID: 20260812-integrate-rds-postgres-4e61c2
- Mode: Integration
- Branch: codex/20260812-integrate-rds-postgres-4e61c2-integrate-rds-postgres-4e61c2
- Worktree: D:\Datas\OthersProjects\NianAIGC-integration-rds-4e61c2
- Base commit: 84d84ba94f136f10624700e8d34ed19fc6fe7fe7
- Owner: codex
- Status: Planning
## Scope
- Integrate feature commit `84d84ba94f136f10624700e8d34ed19fc6fe7fe7` into the default branch.
- Promote the completed RDS/ACK task's durable backend, migration, workload, and operational boundaries into canonical project memory.
- Preserve the pre-existing project-document initialization in the occupied `main` worktree without adopting unrelated application changes.
## Intent And Constraints
- Use an exclusively owned integration worktree and repository integration lock.
- Do not overwrite or delete the untracked `.project-docs` files in the occupied `main` worktree unless byte-equivalence with the committed initialization baseline is verified.
- Record only confirmed RDS/ACK architecture and deployment facts; leave unrelated placeholder project positioning/domain memory untouched.
- Keep live RDS migration, Docker runtime, and ACK rollout explicitly unverified.
## Outcome
- Integration in progress.
## Verification
- Source feature commit `84d84ba` is present and based directly on `main` through initialization commit `0bcb149`.
- Source task final and incremental Sol reviews returned `PASS`.
## Follow-ups
- None recorded.
## Promotion Candidates
- None recorded.