Nginx / {{ config.id }}
{{ config.path }}
{{ 'Enabled' if config.enabled else 'Disabled / shared config' }} · {{ config.ownership }} · {{ config.domains|join(', ') }}
{% if config.project %}Open project {{ config.project }} · Project edits are applied and preserved across deployments.
{% endif %}Save tests the active Nginx configuration. Save & reload also activates the change. Keep privileged include, log, certificate and module directives unchanged. Disabled files remain unverified until enabled.
{{ config.roots|join(', ') or 'Proxy target — see Services for working directory' }}
{{ config.upstreams|join(', ') }}
Find related services & processes →{{ config.certificates|join(', ') or 'No certificate directive in this file' }}
{{ config['keys']|join(', ') }}
DEPLOY → VERIFY → SWITCH → STOP OLD SERVICES
Create a Git deployment project without a domain, then select it here. We deploy and health-check it first, preserve this Nginx file’s settings, copy its SSL files, switch its backend or static root, and stop the selected old services. A failed build leaves this website untouched.
Supports one direct loopback HTTP backend or one static root. Database, uploads and environment variables are not copied—prepare these on the replacement project first. Old services are stopped, not disabled at boot.
Adopt this website in place. Existing files, certificate paths and running processes stay in place. This adds operational management; Git-based releases remain a separate deployment project.
Disabling takes the website out of Nginx. Deleting removes this config and its enabled links, with a recoverable backup. Neither action removes app files, certificates, or stops its backend service.