nf

Remotes

Repo remotes connect an nf project repository to cached remote env IDs. They are stored in nf.json under remotes.

Add a Remote

Refresh the site cache first when needed:

nf site refresh
nf site list --envs

Add a remote from the project repo:

nf remote add production client.app1-linode:live

nf remote add validates that the requested site/env exists in the local cache before writing nf.json. The env ref format is:

<site>.<target>:<env>

Examples:

client.app1-linode:live
client.app1-linode:staging
client.kinsta:live

Inspect Remotes

nf remote list
nf remote show production

nf remote show <name> prints the env ID, provider, target, URL, and access details when the cache has a matching env.

Use Remotes

Commands that accept repo remotes include:

nf theme deploy production --dry-run
nf theme rollback production --dry-run
nf alias status production
nf alias sync production
nf plugin status production
nf env logs production
nf env pull production --dry-run
nf domain list production

Keep remotes pointed at env IDs, not public domains. A public launch changes domain bindings for the env; it should not change nf.json remotes.

Remove a Remote

nf remote remove production

This removes the repo metadata entry only. It does not modify the remote site/env.