DEVELOPMENT / DEPLOY ENVIRONMENTS

Live, Stage, and UAT

Publish isolated remote versions without editing the .env file used by dowe dev.

1 / LOCAL PROFILES

One local profile per environment

Declare shared variable names in .env.example. Process environment values take precedence over the selected local file, and Dowe never falls back to another profile. Keep all four value files in .gitignore; they are compiler inputs and are never copied into deployment packages.

dowe
.env
.env.live
.env.stage
.env.uat

2 / DEPLOY FLOW

Select the environment first

Interactive deploy asks for Live, Stage, or UAT before it asks for the Server or Web surface. Scripts use --environment; Live is the default.

dowe
dowe deploy
dowe deploy web --environment stage --publish
dowe deploy web --environment uat --publish
dowe deploy server --environment live --target cloudflare --publish
dowe deploy web --environment stage --target vercel --name clinic-web --publish
Environment
Purpose
Behavior

No data

There are no records to display

3 / PREVIEW ACCESS

Protect previews without changing Live

Stage and UAT require a server-only DOWE_DEPLOY_ACCESS_PASSWORD with at least 12 characters. Browsers receive an HTTP Basic Auth challenge before any app route or static asset runs.

Concern
Rule

No data

There are no records to display

dowe
DOWE_DEPLOY_ACCESS_PASSWORD=use-a-long-private-password