Repository Hygiene: Remove Tracked Secrets and Runtime Databases #6

Closed
opened 2026-03-29 08:35:00 -05:00 by yusiboyz · 0 comments
Owner

This issue covers removal of tracked secrets, env files, and runtime databases.

Problems:

  • .env files are tracked in the repository
  • SQLite database files are tracked in the repository
  • This creates repo-level exposure of operational configuration and data

Files/artifacts:

  • .env
  • frontend-v2/.env
  • services/fitness/.env
  • services/trips/.env
  • gateway/data/*.db
  • services/fitness/data/*.db
  • services/trips/data/*.db

Acceptance criteria:

  • No live .env or .db artifacts remain tracked in git
  • .gitignore blocks future accidental commits of these artifacts
  • Relevant credentials are rotated
  • Historical exposure is addressed as appropriate for the deployment
This issue covers removal of tracked secrets, env files, and runtime databases. Problems: - `.env` files are tracked in the repository - SQLite database files are tracked in the repository - This creates repo-level exposure of operational configuration and data Files/artifacts: - .env - frontend-v2/.env - services/fitness/.env - services/trips/.env - gateway/data/*.db - services/fitness/data/*.db - services/trips/data/*.db Acceptance criteria: - No live `.env` or `.db` artifacts remain tracked in git - `.gitignore` blocks future accidental commits of these artifacts - Relevant credentials are rotated - Historical exposure is addressed as appropriate for the deployment
yusiboyz added this to the Immediate milestone 2026-03-29 08:43:50 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: yusiboyz/platform#6