cwp edge

shipped 1.0.0

cwp edge [flags]

cwp edge groups the commands below and takes no action of its own; run it alone and it prints its help.

Flag	What it does	Default
`--with-agent`	with —dry-run on a host with no shell: install and remove the PHP agent so the plan is real	`off`

Subcommand	What it does
`cwp edge pull`	Read the zone’s settings into edge/.yml
`cwp edge push`	Write edge/.yml to the zone (an upward write against a remote)
`cwp edge status`	Compare edge/.yml with what the zone holds, and write nothing
`cwp edge captcha`	Provision the edge’s captcha widget and write its keys into the builder (F-137)

What it does

cwp edge reads, converges and compares the settings of the edge in front of an environment: the reverse proxy or CDN that stands between visitors and the origin (ADR-031). It has four verbs.

cwp edge pull <env> reads the zone into edge/<env>.yml.
cwp edge push <env> writes that file back to the zone.
cwp edge status <env> names the drift between the two.

The file carries TLS mode, script rewriting and email obfuscation. It does not carry DNS: a zone holds records for mail and for services cwp knows nothing about, and no flag puts them in the tree.

The environment declares its edge in cwp.yml:

environments:
  live:
    edge:
      id: cloudflare
      zone: example.com

The token comes from CWP_<ENV>_EDGE_TOKEN or ~/.config/cwp/edge.yml, never from cwp.yml. cwp edge push needs the token to carry Zone Settings:Edit.

What it does not do

It does not manage DNS. Records stay at the edge, untouched.
It does not touch an environment with no edge: block.