mirror of
https://github.com/sartography/spiff-arena.git
synced 2025-02-12 09:27:00 +00:00
584be1df6a
* kill tags * big four * move doc script * move dev to explain * move images to root because it is better * move scrit * script * move out * moved building_diagrams * couple devops things * docs * move exe * unit test * articlers * wip * path * devops * perm * deploy * stuff * everything * broken links * wip --------- Co-authored-by: burnettk <burnettk@users.noreply.github.com>
32 lines
928 B
Markdown
32 lines
928 B
Markdown
# Deployment
|
|
|
|
The minimal deployment is to mimic the docker-compose.yml file at the root of spiff-arena.
|
|
Steps for a more hardened production setup after that baseline include:
|
|
|
|
1. Setting up a MySQL or PostgreSQL database for Backend persistence (instead of SQLite)
|
|
2. Setting up a Redis/Valkey or RabbitMQ server for a Celery broker.
|
|
3. Separating out the Backend deployment into three deployments: 1) API, 2) Background, and 3) Celery worker.
|
|
|
|
```mermaid
|
|
graph TD;
|
|
subgraph Backend
|
|
A[API]
|
|
B[Background]
|
|
Ce[Celery Worker]
|
|
end
|
|
F[Frontend]
|
|
Co[Connector Proxy]
|
|
D[Database]
|
|
A --> D
|
|
B --> D
|
|
Ce --> D
|
|
F -- Communicates with --> Backend
|
|
Backend -- delegates to --> Co
|
|
```
|
|
|
|
API, Celery Worker, Connector Proxy, and Frontend can run any number of replicas.
|
|
The Background container is like a cron container, so it should run only one replica.
|
|
|
|
```{tags} how_to_guide
|
|
```
|