cwp access

cwp access [env] [flags]

This name is an alias. The work moved to cwp perimeter, and that page documents it. This spelling still runs for one minor cycle.

Acts on the local site. Name an environment to act there instead.

tree → site

Argument	What it is	Default
[env]	environment to converge (default: the local site)

Flag	What it does	Default
--status	report declared vs. effective per door and environment, knock on each from outside, and write nothing	off
--force	override the protected-environment refusal	off
--no-backup	skip the remote backup taken before the write	on
--yes	skip the confirmation prompt	off
--with-agent	with —dry-run on a host with no shell: install and remove the PHP agent so the plan is real	off

Plus the shared flags --json, -v, --verbose, -q, --quiet and --dry-run.

What it does

cwp access is the former name of the site door of cwp perimeter, kept as an alias for one minor cycle. It runs the same command. access: <env>: <mode> in cwp.yml reads as perimeter.<env>.site: open is public, maintenance and coming_soon keep their names.

# was
access:
  dev: coming_soon

# is
perimeter:
  dev:
    site: coming_soon

The perimeter page has the doors, the levels and what each enforcer does.

What it does not do

• It does not take a mode argument. The map is the only switch, as before.
• It adds nothing to the old behaviour. The other doors are the new command’s; this name converges the site door and reports the new spelling.