Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 5 additions & 7 deletions .env.example
Original file line number Diff line number Diff line change
Expand Up @@ -40,9 +40,11 @@ SOCIAL_CONTENT_LLM_FALLBACK_MODEL=gpt-5.4
SOCIAL_CONTENT_LLM_TIMEOUT=60

# ── Database ──────────────────────────────────────────────────
# Local default is SQLite when OPS_DATABASE_URL is unset. For the Postgres
# migration/dev path, start docker-compose.postgres.yml and use:
# OPS_DATABASE_URL=postgresql+psycopg://synapse_growing:synapse_growing_dev@127.0.0.1:54329/synapse_growing
# PostgreSQL is required for runtime, local dev, tests, and CI.
# Start docker-compose.postgres.yml locally and use:
OPS_DATABASE_URL=postgresql+psycopg://synapse_growing:synapse_growing_dev@127.0.0.1:54329/synapse_growing_local
# Optional dedicated test DB. CI sets this explicitly.
OPS_TEST_POSTGRES_URL=postgresql+psycopg://synapse_growing:synapse_growing_dev@127.0.0.1:54329/synapse_growing_test
# OPS_DB_POOL_SIZE=12
# OPS_DB_MAX_OVERFLOW=24

Expand Down Expand Up @@ -182,9 +184,5 @@ OPS_PORT=9600
OPS_LOG_LEVEL=debug
X_OAUTH_REDIRECT_URI=http://127.0.0.1:9600/api/social/x/oauth/callback

# ── Database ──────────────────────────────────────────────────
# OPS_DB_PATH=
# OPS_DATABASE_URL=

# ── CORS ──────────────────────────────────────────────────────
OPS_CORS_ORIGINS=*
44 changes: 44 additions & 0 deletions .github/workflows/pr-ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,8 @@ concurrency:

env:
RIPGREP_VERSION: "15.1.0"
OPS_DATABASE_URL: postgresql+psycopg://synapse_growing:synapse_growing_dev@127.0.0.1:5432/synapse_growing_test
OPS_TEST_POSTGRES_URL: postgresql+psycopg://synapse_growing:synapse_growing_dev@127.0.0.1:5432/synapse_growing_test

jobs:
scope:
Expand Down Expand Up @@ -95,6 +97,20 @@ jobs:
needs: scope
if: needs.scope.outputs.run_full == 'true'
runs-on: ubuntu-latest
services:
postgres:
image: postgres:16-alpine
env:
POSTGRES_DB: synapse_growing_test
POSTGRES_USER: synapse_growing
POSTGRES_PASSWORD: synapse_growing_dev
ports:
- 5432:5432
options: >-
--health-cmd "pg_isready -U synapse_growing -d synapse_growing_test"
--health-interval 5s
--health-timeout 5s
--health-retries 20
steps:
- uses: actions/checkout@v4
with:
Expand Down Expand Up @@ -178,6 +194,20 @@ jobs:
needs: scope
if: needs.scope.outputs.run_full != 'true' && needs.scope.outputs.run_backend == 'true'
runs-on: ubuntu-latest
services:
postgres:
image: postgres:16-alpine
env:
POSTGRES_DB: synapse_growing_test
POSTGRES_USER: synapse_growing
POSTGRES_PASSWORD: synapse_growing_dev
ports:
- 5432:5432
options: >-
--health-cmd "pg_isready -U synapse_growing -d synapse_growing_test"
--health-interval 5s
--health-timeout 5s
--health-retries 20
steps:
- uses: actions/checkout@v4
with:
Expand Down Expand Up @@ -284,6 +314,20 @@ jobs:
needs: scope
if: needs.scope.outputs.run_full != 'true' && needs.scope.outputs.run_scope_self_test == 'true'
runs-on: ubuntu-latest
services:
postgres:
image: postgres:16-alpine
env:
POSTGRES_DB: synapse_growing_test
POSTGRES_USER: synapse_growing
POSTGRES_PASSWORD: synapse_growing_dev
ports:
- 5432:5432
options: >-
--health-cmd "pg_isready -U synapse_growing -d synapse_growing_test"
--health-interval 5s
--health-timeout 5s
--health-retries 20
steps:
- uses: actions/checkout@v4
with:
Expand Down
4 changes: 2 additions & 2 deletions dashboard/src/pages/ProductionDeployModal.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ export default function ProductionDeployModal({
<FieldLabel>输入确认短语</FieldLabel>
<input
className="w-full rounded-2xl border border-[color:var(--ops-stroke-strong)] bg-[color:var(--ops-panel)] px-4 py-3 font-mono text-sm"
placeholder="DEPLOY_PRODUCTION"
placeholder="YES"
value={confirmPhrase}
onChange={(event) => onConfirmPhraseChange(event.target.value)}
/>
Expand All @@ -71,7 +71,7 @@ export default function ProductionDeployModal({
<button
type="button"
className="rounded-xl border border-[color:var(--ops-state-blocked-border)] bg-[color:var(--ops-state-blocked-bg)] px-4 py-2.5 text-sm font-semibold text-[color:var(--ops-state-blocked-text)] disabled:opacity-50"
disabled={confirmPhrase !== 'DEPLOY_PRODUCTION' || Boolean(busyAction) || !gateReady}
disabled={confirmPhrase !== 'YES' || Boolean(busyAction) || !gateReady}
onClick={onDeploy}
>
{busyAction === busyKey ? '发布中…' : '确认发布到 production'}
Expand Down
8 changes: 5 additions & 3 deletions dashboard/src/pages/ReleaseTaskDetailPanel.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -147,9 +147,11 @@ export function ReleaseTaskDetailModal({
const taskMetadata = (task as ReleaseTask & { task_metadata?: Record<string, unknown> }).task_metadata || {}
const attachedPrebuiltImage = metadataString(taskMetadata, 'prebuiltImageDigest')
const attachedPrebuiltCommit = metadataString(taskMetadata, 'sourceCommitSha')
const canAttachPrebuiltImage = task.environment === 'staging'
const isPrebuiltFrontendTask = task.environment === 'staging'
&& task.project_key === 'synapse-network'
&& ['user-front', 'docs-front'].includes(task.service_key || '')
&& ['admin-front', 'user-front', 'docs-front'].includes(task.service_key || '')
const canAttachPrebuiltImage = task.environment === 'staging'
&& isPrebuiltFrontendTask
&& task.status === 'requested'
&& !task.deployment_record_id
&& Boolean(onAttachPrebuiltImage)
Expand Down Expand Up @@ -198,7 +200,7 @@ export function ReleaseTaskDetailModal({
{task.note ? <div className="mt-4 rounded-xl bg-[color:var(--ops-panel)] p-3 text-sm text-[color:var(--ops-text-muted)]">{task.note}</div> : null}
</section>

{task.environment === 'staging' && ['user-front', 'docs-front'].includes(task.service_key || '') ? (
{isPrebuiltFrontendTask ? (
<section className="rounded-2xl border border-[color:var(--ops-stroke-soft)] bg-[color:var(--ops-panel-subtle)] p-4">
<h3 className="text-sm font-semibold uppercase tracking-[0.18em] text-[color:var(--ops-text-caption)]">Prebuilt Image</h3>
{attachedPrebuiltImage ? (
Expand Down
4 changes: 2 additions & 2 deletions dashboard/src/pages/ReleasesPage.production.test.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -130,14 +130,14 @@ describe('ReleasesPage production deploy', () => {
expect(await screen.findByText('prod-main-sha')).toBeTruthy()
expect(screen.getByText('Deployment #71')).toBeTruthy()
const initialTaskPageCalls = apiMock.getReleaseTasksPage.mock.calls.length
await user.type(screen.getByLabelText('输入确认短语'), 'DEPLOY_PRODUCTION')
await user.type(screen.getByLabelText('输入确认短语'), 'YES')
await user.click(screen.getByRole('button', { name: '确认发布到 production' }))

await waitFor(() => {
expect(apiMock.deployReleaseTask).toHaveBeenCalledWith(42, {
actor: 'operator',
note: 'Manual staging release',
confirm_phrase: 'DEPLOY_PRODUCTION',
confirm_phrase: 'YES',
})
})
expect(apiMock.getReleaseTasksPage).toHaveBeenCalledTimes(initialTaskPageCalls)
Expand Down
4 changes: 2 additions & 2 deletions docker-compose.postgres.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,15 +4,15 @@ services:
container_name: synapse-growing-postgres
restart: unless-stopped
environment:
POSTGRES_DB: synapse_growing
POSTGRES_DB: synapse_growing_local
POSTGRES_USER: synapse_growing
POSTGRES_PASSWORD: synapse_growing_dev
ports:
- "54329:5432"
volumes:
- synapse-growing-postgres-data:/var/lib/postgresql/data
healthcheck:
test: ["CMD-SHELL", "pg_isready -U synapse_growing -d synapse_growing"]
test: ["CMD-SHELL", "pg_isready -U synapse_growing -d synapse_growing_local"]
interval: 5s
timeout: 5s
retries: 20
Expand Down
4 changes: 2 additions & 2 deletions docs/design-docs/current-feature-inventory.md
Original file line number Diff line number Diff line change
Expand Up @@ -105,15 +105,15 @@
5. PR / release 只信任 workflow evidence、verification verdict 和 human gate decision。
6. Drop Goal 不会自动 rollback;下线已发布功能必须创建 decommission requirement。
7. `release_pr_status_sweep` 会只读同步 GitHub PR 状态:merged PR 更新为 `merged`,closed / missing PR 收敛为 `pr_closed / abandoned`,但不会自动 deploy 或 rollback。
8. `/releases` 的 `发布管理` 分面使用独立 Release Task 记录手动和需求流转发布意图;Release Task 不等于 Deployment Record。任务创建不会自动部署,分支选择从目标 GitHub 仓库 branch list 读取;`main` 分支可由 Operator 直接点击 `发布到 staging`,其它分支没有 open/merged PR 时只能提交 PR,PR checks 通过后才允许触发白名单发布 runner。Production 发布已接入 Human-Gated Release Task:只允许 `main`,必须同一 project / service / commit 已有 staging success,并要求 operator 输入 `DEPLOY_PRODUCTION` 后 dispatch 模块化 production workflow。当前一等发布目标包含 `Synapse-Network` 的 gateway / gateway-admin / admin-front / user-front / docs-front,以及 `Synapse-Network-Provider` 的 provider-service。`Synapse-Network` staging dispatch 按 runtime family 选择 workflow:gateway -> `deploy-staging-gateway.yml`,gateway-admin/admin-front -> `deploy-staging-admin.yml`,user-front/docs-front -> `deploy-staging-frontends.yml`;目标仓库的 `deploy-staging.yml` 只作为 reusable core / compatibility runner。Production dispatch 同样按模块选择 workflow:gateway -> `deploy-production-gateway.yml`,gateway-admin -> `deploy-production-admin.yml`,admin-front/user-front/docs-front -> `deploy-production-frontends.yml`,provider-service -> `deploy-production-provider.yml`;所有 production runner 通过 GCP WIF 部署到 `synapse-network-prod`。
8. `/releases` 的 `发布管理` 分面使用独立 Release Task 记录手动和需求流转发布意图;Release Task 不等于 Deployment Record。任务创建不会自动部署,分支选择从目标 GitHub 仓库 branch list 读取;`main` 分支可由 Operator 直接点击 `发布到 staging`,其它分支没有 open/merged PR 时只能提交 PR,PR checks 通过后才允许触发白名单发布 runner。Production 发布已接入 Human-Gated Release Task:只允许 `main`,必须同一 project / service / commit 已有 staging success,并要求 operator 输入 `YES` 后 dispatch 模块化 production workflow。当前一等发布目标包含 `Synapse-Network` 的 gateway / gateway-admin / admin-front / user-front / docs-front,以及 `Synapse-Network-Provider` 的 provider-service。`Synapse-Network` staging dispatch 按 runtime family 选择 workflow:gateway -> `deploy-staging-gateway.yml`,gateway-admin -> `deploy-staging-admin.yml`,admin-front/user-front/docs-front -> `deploy-staging-frontends.yml`;目标仓库的 `deploy-staging.yml` 只作为 reusable core / compatibility runner。`admin-front/user-front/docs-front` staging Release Task 可绑定本地 ephemeral worktree 预构建的 immutable Artifact Registry digest,绑定后 frontend workflow 校验 `prebuilt_image_digest` 并跳过 Cloud Build,直接按 digest 部署、smoke 和记录 manifest;该能力只开放 staging frontend,不开放 production。Production dispatch 同样按模块选择 workflow:gateway -> `deploy-production-gateway.yml`,gateway-admin -> `deploy-production-admin.yml`,admin-front/user-front/docs-front -> `deploy-production-frontends.yml`,provider-service -> `deploy-production-provider.yml`;所有 production runner 通过 GCP WIF 部署到 `synapse-network-prod`。
9. Release Task detail modal 展示 PR gate、DeploymentRecord、GitHub Actions run link、health check、failure summary 和 deployment metadata;Synapse-Network 与 Synapse-Network-Provider staging runner 都使用 GCP Workload Identity Federation + Cloud Build + Cloud Run,不使用长生命周期 GCP service account JSON key 或 SSH deploy secrets;Provider DeploymentRecord 标记 `deploy_strategy=github_actions_wif_cloudrun`。
10. `/releases` 的 `上线记录` 分面只读展示成功的 `DeploymentRecord(status=succeeded)`,不混入 pending / failed / cancelled Release Task。手动标记 Release Task 已完成时,后端会创建或绑定一条 `manual_completion` 成功 DeploymentRecord 后再进入上线记录。上线记录用于确认 GitHub Actions、Cloud Run revision / image / manifest、health check 和 rollback target,并可按 `staging` / `production` 过滤。
11. 没有 webhook callback 的本地发起 staging 部署,由全局 `release_deployment_status_sweep` 定时拉取 GitHub Actions run 结果,也可通过 `/releases` 的 `同步状态` 人工触发同一幂等同步函数;同步只处理未终态 DeploymentRecord,只读吸收外部事实,不触发 deploy / merge / rollback。点击 `发布到 staging` 后 Release Task 进入 `deploying / 自动检查中`,健康检查事实由 GitHub Actions runner 内的 Cloud Run smoke check 负责,Ops Console 只同步 Actions success/failure 和 smoke metadata。人工 completed / failed / cancelled 终态优先,不会被后台同步回滚。
12. Staging 发布分两类:`main` 分支可直接由 Operator 点击 `发布到 staging`;非 main 分支不要求先合并 `main`,但必须存在 PR 且 PR checks 通过。Production v1 只允许从 `main` 的 verified staging commit 推进,并必须经过 Growing Human Gate 与 GitHub Environment `production` 双门禁。
13. Rollback 不由 Drop Goal、普通 Release Task PATCH 或 staging 快捷按钮触发。Runtime rollback 以历史成功上线记录的 commit / image / manifest 为 target 并进入 Human Gate;代码级 revert 必须走新分支、PR、checks、merge 和正常发布链路。
14. `/releases` 的 `定时任务发布` 分面管理 Synapse-Network 部署在 Google 上的 Cloud Run Jobs:gateway 周期任务 `deposit-indexer`、`provider-withdraw-reaper`、`consumer-withdraw-processor`、`notification-outbox-drain`、`in-app-cleanup`,以及 gateway / gateway-admin migration jobs。Operator 先通过 `创建定时任务发布` 选择 staging 环境、GitHub 分支和具体 job 名称,系统只创建 `scheduled_job_release_tasks(status=requested)`,不会 dispatch;只有在列表中点击 `发布到 staging` 才创建 `DeploymentRecord(trigger_source=scheduled_job_release)` 并 dispatch `deploy-staging-jobs.yml`。
15. 定时任务发布状态以 `scheduled_job_release_tasks` 为 UI source of truth;物理执行结果来自关联 DeploymentRecord、GitHub Actions callback / sync 和 `jobsManifest`。全局 `release_deployment_status_sweep` 与手动 `同步状态` 都会同步普通 Release Task 和定时任务发布任务。Google 写操作、单 job image 更新、可选 smoke / migration execution 全部在 GitHub Actions + WIF 中完成,本机 API 不调用 `gcloud`。Scheduler freshness 是健康信号,不等同发布失败;migration jobs 是发布时手动/受控执行任务,不做 freshness 警报。
16. 本地主库支持 Docker Postgres。`OPS_DATABASE_URL=postgresql+psycopg://synapse_growing:synapse_growing_dev@127.0.0.1:54329/synapse_growing` 可将应用切到 Postgres;`scripts/db/migrate_sqlite_to_postgres.py` 负责从 `server/ops.db` 全量迁移所有现有表和数据,`scripts/db/validate_postgres_migration.py` 校验每表 row count,`scripts/db/run_sql_migrations.py` 通过 `schema_migrations` 幂等执行后续 SQL。完整操作记录见 `docs/ops/05_Postgres_Migration_and_E2E_Runbook.md`。
16. 本地主库已切换为 PostgreSQL-only。`OPS_DATABASE_URL` 必须是 PostgreSQL URL,例如 `postgresql+psycopg://synapse_growing:synapse_growing_dev@127.0.0.1:54329/synapse_growing_local`;缺失或 SQLite URL 会 fail closed。`scripts/db/migrate_sqlite_to_postgres.py` 只负责从历史 `server/ops.db` 一次性导入现有表和数据,`scripts/db/validate_postgres_migration.py` 校验每表 row count/hash,`scripts/db/run_sql_migrations.py` 通过 `schema_migrations` 幂等执行后续 SQL。完整操作记录见 `docs/ops/05_Postgres_Migration_and_E2E_Runbook.md`。

## 4.5 Social Publishing

Expand Down
Loading
Loading