Theme
Edit a site
Edit Site (from Manage or the actions menu) changes runtime and routing settings without recreating the site.
Who can use this page? write/manage on the site — site owners. Some fields need manage.
Common settings
| Setting | Notes |
|---|---|
| Domain | Primary hostname shown in the panel |
| Active | Enable or suspend the site |
| PHP version | PHP/WordPress sites only |
| Node.js version | Node sites |
| Python version | Python sites (3.10–3.14) |
| App Port / Internal Port | Port Nginx uses to reach Node/Python/container app |
| SPA mode | Static sites — fallback to index.html |
| Proxy target | Reverse Proxy sites — upstream URL |
| Dockerfile / Internal Port / Persistent Data Path | Dockerfile Apps; deployment health checks are set in Git Deployment |
Apex / WWW redirect control
A control on the site determines whether NitHost redirects between apex and www. It does not rewrite WordPress/application URLs or issue certificates by itself.
For cross-domain redirects (send traffic to another HTTP(S) domain), use Domain redirects under Site Routing.
Git deployment settings (Node / Python / Dockerfile)
Open Site Actions → Git Deployment for the repository build settings below. They do not configure the manual Node upload actions in Edit Site. See the Node upload workflow.
| Field | Purpose |
|---|---|
| Application root | Repo subdirectory (monorepo) |
| Build command | Node default: install dependencies + npm run build --if-present |
| Frontend asset build command | Optional Node build before Python venv (Python sites) |
| Start command | How the app process starts |
| Health check path | Must return non-5xx without auth |
| Dockerfile | Path relative to app root (Dockerfile Apps) |
Repository contracts: Node.js & Python, Dockerfile.
Saving
Click Save / Save changes. Runtime fields may require a restart of the Node/Python/container app from Site actions.