List view

• GCP beta deployment

  Prepare and execute the first controlled beta deployment of the TRAQ server to GCP using Cloud Run, Cloud SQL, Cloud Storage, Artifact Registry, and Secret Manager. - Goal - Track the first controlled beta deployment of the standalone server repo to GCP. - Current baseline - Standalone repo exists - uv workflow works - Alembic is in place - Docker image builds and local smoke test passed - GCS artifact backend exists - GitHub Pages docs workflow exists - Target deployment shape - Cloud Run - Cloud SQL for PostgreSQL - Cloud Storage for artifacts - Artifact Registry - Secret Manager - Execution checklist - choose concrete GCP names - enable required services - provision Artifact Registry - provision Cloud Storage bucket - provision Cloud SQL instance/database/user - create runtime secrets: - TRAQ_API_KEY - OPENAI_API_KEY - TRAQ_DATABASE_URL - build and push first image - run uv run alembic upgrade head against Cloud SQL - deploy Cloud Run with production flags: - TRAQ_ARTIFACT_BACKEND=gcs - TRAQ_ENABLE_DISCOVERY=false - TRAQ_AUTO_CREATE_SCHEMA=false - TRAQ_ENABLE_FILE_LOGGING=false - validate: - /health - device registration - approval/token flow - assigned jobs - submit/final - artifacts in GCS - Acceptance criteria - First cloud environment is live and usable for controlled beta. - Runtime state is in Cloud SQL. - Artifacts are written to Cloud Storage. - Operator CLI can still administer the environment from a trusted operator setup. - Notes - Use docs/gcp_deployment_runbook.rst as the detailed operator reference.

  Overdue by 4 month(s)

  •

  Due by March 20, 2026

  •0/1 issues closed
  0% complete1 open0 closed