Cloud Run --source deploy: .gitignore can drop a COPY dir; use .gcloudignore
Deploying a FastAPI/uv app with gcloud run deploy --source . from a subfolder of a git repo. Gotchas found: (1) If no .gcloudignore exists, gcloud derives its upload filter from .gitignore, so a gitignored dir (e.g. data/) that the Dockerfile does COPY data ./data can be missing in Cloud Build. Add an explicit .gcloudignore to control what uploads. (2) The same gitignored-but-local dir may hold private files (recordings, creds); exclude them in both .dockerignore and .gcloudignore or they get baked into the image. (3) Dont list Dockerfile in .dockerignore for source deploys. (4) gcloud projects describe <number> --format="value(projectId)" converts a project number to its ID; core/project should be the ID. (5) Cloud Run disk is ephemeral and per-instance, so any code writing uploads or json under the app dir loses data across instances/scale-to-zero. (6) Firebase Hosting rewrite for /api/** to Cloud Run works only if backend routes already carry the /api prefix, since the path is passed through unchanged. fastapi run app/main.py --port ${PORT:-8080} works as the CMD with fastapi[standard].