cwp fetch

cwp fetch [env] [flags]

Acts on dev unless another environment is named.

Argument	What it is	Default
[env]	environment to fetch from	dev

Flag	What it does	Default
--themes	themes only	off
--plugins	plugins only	off
--yes	skip the overwrite confirmation	off

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

What it does

Brings third-party themes and plugins down from an environment.

They are gitignored — cwp moves code upward only — so a freshly initialised project has a database that references a theme which is not on disk. This is the command that closes that gap, and it is normally run once, right after cwp init.

It lists the remote directories, skips everything inside a tracked path, asks before overwriting local directories that already exist, and transfers each remaining directory on its own. Your site plugin is never in the blast radius.

Each directory travels as a tarball — remote tar, then pull the archive, then extract locally — because cloudron sync pull exits 0 having transferred nothing in Cloudron CLI 8.2.6 (B-003). Every transfer is then checked against the remote file count: cwp will not report success over an empty directory.

Example

cwp fetch                  # themes and plugins from dev
cwp fetch --themes --yes   # just the themes, no prompt

What it does not do

It writes nothing upward, touches no tracked path, and installs or activates nothing.

It does not decide what should be installed. That inventory is cwp plugins, and the two answer different questions: fetch copies what is there, plugins records and reproduces what ought to be.