Running The Backend In Docker¶
The backend service can run independently in Docker and pairs with the documented Docker-based NetBox plugin installation workflow.
Pull And Run¶
docker pull emersonfelipesp/proxbox-api:latest
docker run -d --name proxbox-api -p 8800:8000 emersonfelipesp/proxbox-api:latest
Notes¶
- Port
8800is the default backend port expected by the sample configuration. - The container exposes
8000internally (nginx in front of uvicorn), so map host8800to container8000. - If you publish a different port, make the same change in the
FastAPIEndpointobject inside NetBox. - If you front the container with TLS or a reverse proxy, configure the NetBox endpoint object accordingly.
- For HTTPS in local or staging environments, use
emersonfelipesp/proxbox-api:latest-nginxand point the NetBoxFastAPIEndpointathttps://<host>:8800withverify_ssldisabled (the mkcert cert is self-signed; tick enabled only after installing the mkcert root CA into NetBox's trust store). - The backend image keeps nginx buffering off for
/streamendpoints, so SSE progress stays chunked even when the service is proxied. - To use your own CA-signed or Let's Encrypt certificate, mount it read-only at
/certs(the directory must containcert.pemandkey.pem); mkcert generation is automatically skipped. With a trusted certificate you can also enableverify_sslon theFastAPIEndpoint.