nf env push and nf env pull sync the database and mutable wp-content between the local env and a configured repo remote.
Database and uploads sync are high risk. Treat every production push as potentially destructive.
Pull remote data into local development:
nf env pull production --dry-run
Push local data to a remote env:
nf env push production --dry-run
If you omit the remote, nf prompts you to choose from configured repo remotes:
nf env pull --dry-run
In non-interactive mode, provide the remote explicitly.
Sync includes:
wp-content/uploadswp-content/pluginswp-content/mu-pluginswp-content/languagesTheme deployment is separate. Use Themes for theme releases.
Dry-run prints the local project, local env path, remote name, site, env, provider, URL, access summary, and mode:
nf env pull production --dry-run
nf env push production --dry-run
No data is changed in dry-run mode.
Non-interactive preflight without execution is also non-mutating:
nf env pull production --non-interactive
Interactive execution prompts for confirmation:
nf env pull production
nf env push production
Non-interactive execution requires both --execute and --yes:
nf env pull production --execute --yes --non-interactive
nf env push production --execute --yes --non-interactive
Before pulling remote data into local:
nf remote show <remote>.--dry-run and read the plan.Before pushing local data to a remote:
wp-content.--dry-run and read the plan.Key rule: never silently clobber production credentials or content.