backend_website

nginx HTTPS vhost that serves a static build from dist/ and reverse-proxies everything else to a backend process listening on 127.0.0.1:<port>. Pairs with fastapi_backend (or any process bound to localhost) to expose it publicly over HTTPS. If the domain has no static frontend of its own (pure API), that's fine — dist/ can simply not exist, and every request falls through to the proxy.

What it does

1. Templates the HTTPS vhost to /etc/nginx/sites-enabled/<backend_website_server_name>.https.conf:
2. optional redirect vhost for backend_website_alternate_server_name (e.g. a www. domain) straight to the primary domain,
3. root <site_root>/dist with try_files $uri @backend,
4. @backend proxies to http://127.0.0.1:<backend_website_port> with the usual X-Forwarded-*/X-Real-IP headers.
5. Reloads nginx.

Variables

Variable	Required	Default	Description
backend_website_server_name	yes	—	Public domain for this vhost. Certificate must already exist (run register_ssl first).
backend_website_port	yes	—	Local port the backend process listens on (127.0.0.1:<port>).
backend_website_alternate_server_name	no	False	Extra domain (e.g. www.<domain>) that 301-redirects to backend_website_server_name. Needs its own register_ssl call/certificate.
backend_website_is_websocket	no	False	Accepted for forward-compatibility but not yet wired into the nginx template — the @backend location has no Upgrade/Connection headers today. Add them to templates/https.conf.j2 before relying on this flag for a websocket backend.

Internally, site_root resolves to /home/{{username}}/projects/{{backend_website_server_name}} — the same convention every other role uses, so it lines up with fastapi_backend's app_root when both target the same fastapi_backend_server_name/backend_website_server_name.

Requirements

• register_ssl must have run for backend_website_server_name (and backend_website_alternate_server_name, if set).
• A backend process actually listening on 127.0.0.1:<backend_website_port> — e.g. fastapi_backend configured with the same fastapi_backend_port.

Example

Paired with fastapi_backend on the same domain/port:

- role: fastapi_backend
  tags: [backend]
  fastapi_backend_repo: my-org/my-api
  fastapi_backend_server_name: my-api.barrins-codex.org
  fastapi_backend_port: 8012
  fastapi_backend_entrypoint: "my_api.main:app"

- role: backend_website
  tags: [backend]
  backend_website_server_name: my-api.barrins-codex.org
  backend_website_port: 8012