3-week reminder — time to take it down
The entre-deux-prod GCP project was temporarily redeployed on 2026-05-04 for resume/job-application linking. The display window is over. Running cost is ~€8-10/month (dominated by the db-f1-micro Cloud SQL instance). Time to delete.
Takedown checklist
Resources that will be deleted
Cloud SQL
entre-deux-db-v2 — us-central1 connection / europe-west1 region (active)entre-deux-db — original instance, currently in MAINTENANCE/SUSPENDED state
Cloud Run services
- us-central1:
entre-deux-api, entre-deux-web
- europe-west1:
entre-deux-api, entre-deux-web, plus unrelated vitalage, vitalens-api, vitalens-web
Artifact Registry
entre-deux-fresh (us-central1)cloud-run-source-deploy (europe-west1)
Secret Manager — all project secrets
Cloud Storage
entre-deux-prod_cloudbuildrun-sources-entre-deux-prod-europe-west1
Demo data is fully reproducible — no SQL export needed
All demo data (Sophie Martin's 3-month diabetes journey) is generated by:
cd backend && python -m scripts.seed_demo
No need to export from Cloud SQL before deleting. If you want an archival snapshot anyway, local SQL dumps from 2026-05-02 are at C:\Users\pyaes\entre-deux\backups\.
Manual cleanup after deletion (both handled in the draft PR)
- Remove the live-demo banner from
README.md (line 18 — the **[Live Demo](...us-central1.run.app)** prefix).
- Revert
.github/workflows/deploy.yml REGION env from us-central1 back to europe-west1 (once GCP's europe-west1 Artifact Registry stale-state has cleared, deploys will target the correct region again).
Changed your mind?
30-day undelete window applies:
gcloud projects undelete entre-deux-prod
3-week reminder — time to take it down
The
entre-deux-prodGCP project was temporarily redeployed on 2026-05-04 for resume/job-application linking. The display window is over. Running cost is ~€8-10/month (dominated by thedb-f1-microCloud SQL instance). Time to delete.Takedown checklist
Delete the GCP project (single command — does everything below in one shot):
This will destroy: Cloud SQL, Cloud Run services, Artifact Registry, Secret Manager secrets, Cloud Storage buckets, and all associated billing. No individual resource cleanup needed.
Merge the pre-staged draft PR (README banner + deploy region revert — link below) after the project is gone.
Resources that will be deleted
Cloud SQL
entre-deux-db-v2— us-central1 connection / europe-west1 region (active)entre-deux-db— original instance, currently in MAINTENANCE/SUSPENDED stateCloud Run services
entre-deux-api,entre-deux-webentre-deux-api,entre-deux-web, plus unrelatedvitalage,vitalens-api,vitalens-webArtifact Registry
entre-deux-fresh(us-central1)cloud-run-source-deploy(europe-west1)Secret Manager — all project secrets
Cloud Storage
entre-deux-prod_cloudbuildrun-sources-entre-deux-prod-europe-west1Demo data is fully reproducible — no SQL export needed
All demo data (Sophie Martin's 3-month diabetes journey) is generated by:
No need to export from Cloud SQL before deleting. If you want an archival snapshot anyway, local SQL dumps from 2026-05-02 are at
C:\Users\pyaes\entre-deux\backups\.Manual cleanup after deletion (both handled in the draft PR)
README.md(line 18 — the**[Live Demo](...us-central1.run.app)**prefix)..github/workflows/deploy.ymlREGIONenv fromus-central1back toeurope-west1(once GCP's europe-west1 Artifact Registry stale-state has cleared, deploys will target the correct region again).Changed your mind?
30-day undelete window applies: