docs(administration): Add reverse proxy paths for containers

ref: #690 closes #674
This commit is contained in:
2025-03-29 13:57:35 +09:30
parent e2182fe37e
commit 26cdd7495a

View File

@ -91,6 +91,18 @@ Centurion ERP uses RabbitMQ for its worker queue. As tasks are created when usin
The [API container](https://hub.docker.com/r/nofusscomputing/centurion-erp) is the guts of Centurion ERP. It provides the endpoints for interacting with Centurion ERP. This container is scalable with the only additional requirement being that a load-balancer be placed in front of all web containers for traffic routing. If deploying to Kubernetes the service load-balancer is sufficient and setting the deployment `replicas` to the number of desired containers is the simplest method to scale.
When setting up the reverse proxy, this container requires the following paths be passed to it:
- `/account/` - Account pages.
- `/admin/` - The Admin pages
- `/api/` - API Pages
- `/sso/` Single Sing on endpoint. This path is optional and only required if you have configured the Authentication to use an SSO service.
- `/static/` - Static assets used by Centurion ERP. i.e. styles, images etc.
### UI Container
@ -99,6 +111,10 @@ The [API container](https://hub.docker.com/r/nofusscomputing/centurion-erp) is t
The [UI container](https://hub.docker.com/r/nofusscomputing/centurion-erp-ui) is the user interface for Centurion. The user interface uses the react framework so as to take advantage of the UI running locally on the users machine. This reduces the bandwidth requirements for using Centurion to be approximatly the data they request and not the page as well.
This container requires that the reverse proxy be setup to path the following path(s):
- `/` - The root path for Centurion ERP. Contains the React Application that is the entire UI
### Background Worker Container
@ -106,6 +122,8 @@ The [Background Worker container](https://hub.docker.com/r/nofusscomputing/centu
Configuration for the worker resides in directory `/etc/itsm/` within the container. see below for the `CELERY_` configuration.
This container does not require any paths be passed to it from the reverse proxy.
## Settings file