status-im/spiff-arena
2
0
Fork 0
mirror of https://github.com/status-im/spiff-arena.git synced 2025-01-18 14:12:44 +00:00
Code Issues Packages Projects Releases Wiki Activity
spiff-arena/docs/DevOps_installation_integration/deployment.md
Kevin Burnett 963d62b323
Proof and ventilate all docs (#1822) 
* let us proof everything

* proof and ventilate everything

* restore removed content

* add back in some headers

* add back more headers

* restore header

* fix header

* fix backend

* restore two long files from main to avoid mangling

* update edit_all for testing

* fix docs

* notes

* more spacing

---------

Co-authored-by: burnettk <burnettk@users.noreply.github.com>
2024-06-26 02:55:03 +00:00

900 B
Raw Blame History

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.
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.