Engineering
Environments & domains
Where E-FACTS runs — local, preview, production domains
Environments & domains
Public domains
| Domain | Role |
|---|---|
| efacts.ca | Public / marketing presence |
| dev.efacts.ca | Internal docs (this site) — planned; gated access |
API hostnames vary by environment — see backend env docs. Do not invent URLs here.
Environment types
| Env | Purpose |
|---|---|
| Local | Developer machines (localhost) |
| Preview | Per-PR / branch deploys (Vercel previews for web) |
| Staging (when present) | Integration testing against non-prod data |
| Production | Live shoppers / public site / gated docs |
Docs deploy posture
This docs site targets Vercel when approved. Prefer preview deployments for review; promote deliberately. Do not deploy until Phase 1 chrome is reviewed (see README).
For production docs, combine:
- App-level docs auth gate (
DOCS_AUTH_*) - Vercel Deployment Protection when appropriate
Config rules
- Env vars via Vercel project settings (web) or Xcode / CI secrets (iOS)
.env.exampleis the contract — never real credentials- Feature flags / API bases differ per env; clients must not assume production defaults in debug builds