Convention: Where should deployment credentials be stored and how should...

Documentation for Sessions

📏 Convention: Where should deployment credentials be stored and how should...

Date: 2026-01-24
Time: 14:39:43 UTC
Session: editor2-64.6
Agent: angular
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

Where should deployment credentials be stored and how should they be accessed?

Task: Credential management convention

🎯 Decision Made

Chosen:

.env.local file (gitignored) with env-loader utility and Railway/GitLab CI variables for production

Options Considered:

Hardcode in code
Environment variables only
.env.local file with env-loader utility
Secrets manager service

💭 Reasoning

Development uses .env.local (gitignored) with the env-loader.js utility that provides getEnvVar() and requireEnvVar() helpers. Production uses Railway environment variables (for internal services) and GitLab CI protected/masked variables (for user platforms). This ensures secrets are never committed while providing consistent access patterns across environments.

📁 Files Involved

tools/scripts/database/env-loader.js
docs/english/Deployment/Reference/environment-variables.md

🔗 Related

Decision ID: dev_1769265583240_vdd5325
Session: 64
Workspace: editor2

Auto-generated by MCP Smart Consolidation