Confirm the plan permits an ASGI server, persistent processes and proxy routing. Identify the application import path, virtual environment and assigned local port or socket.

1. Install the locked application dependencies in the intended environment. Set production configuration and secrets without exposing them through the public directory.

2. Start the application with a supported production ASGI command, using the correct module and app object. Leave development reload mode disabled.

3. Supervise the process through the approved server or panel service. Bind it to the internal endpoint expected by the reverse proxy rather than exposing an unnecessary public port.

4. Configure HTTPS at the appropriate edge, forwarding to the ASGI service. Set trusted proxy handling and path prefixes only for the actual topology.

5. Configure resource limits, private logs and a health check. Document how the service is restarted and how the previous release can be restored.

For a reviewed deployment where the reverse proxy runs on the same Linux server and main.py exports app, an approved supervisor can launch a command shaped like this. Replace the virtual-environment path, module and assigned port with actual service values.

/home/ACCOUNT/apps/api/.venv/bin/python -m uvicorn main:app \
  --host 127.0.0.1 --port 8000 --workers 1 \
  --proxy-headers --forwarded-allow-ips 127.0.0.1

Set the supervisor's working directory and protected environment for this project. The proxy must connect through the stated loopback address and overwrite the trusted forwarded headers. If it is on another host or in a different container network, use the topology-specific supported listener and trust configuration instead.

Expected result: the public HTTPS endpoint responds through the proxy, and the supervisor restores the service after a controlled stop. Leaving this command running in an interactive shell is not a complete production service.

Call a normal endpoint through the public HTTPS hostname and verify the response. Restart the service through the supervisor and confirm it recovers without an interactive terminal.

A proxy 502 may mean the process is not running, the upstream address is wrong or startup failed. Read the ASGI log before increasing proxy timeouts.

• Configuring FastAPI root paths and proxy headers
• Choosing FastAPI workers within a memory budget
• Choosing WSGI or ASGI for Django hosting
• Managing FastAPI lifespan resources and database pools

• FastAPI manual deployment
• FastAPI deployment concepts

• Uvicorn settings