fix: stop tracking .env files with committed secrets

.env.development had a real Postgres/Redis password and JWT secret committed in plain text; .env.test and .env.prod were tracked too. Untrack all .env* files going forward and add .env.example as the onboarding template instead. Note: the exposed dev credentials are still in git history and must be rotated separately. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-08-21 16:10:32 +05:30
parent 9064090949
commit 2093898198
5 changed files with 34 additions and 61 deletions
@@ -1,21 +0,0 @@
-NODE_ENV=development
-PORT=4501
-
-# Nest build
-BUILD_COMMAND=npm run build:development
-
-# Database
-POSTGRES_HOST=postgres
-POSTGRES_DB=support_dev
-POSTGRES_USER=support_user
-POSTGRES_PASSWORD=z1F3tKF1JNDBQmMq95Up
-DATABASE_URL=postgresql://support_user:z1F3tKF1JNDBQmMq95Up@postgres:5432/support_dev
-
-# Redis
-REDIS_HOST=redis
-REDIS_PORT=6379
-REDIS_PASSWORD=D7FJ7QDKo5gF9KQAO1GL
-
-# Security & CORS
-JWT_SECRET=super-secret-development-jwt-key-32-chars-long
-CORS_ORIGINS=https://support-dev.maskantech.in