1.8 KiB
RustBox 0.2.0 Docker variants
The example images are version-pinned where practical so a release does not silently change its integration stack. The bundled SILO topology is for local/integration validation of the S3 API; production deployments should use a security-reviewed S3-compatible service and their own lifecycle/HA policy.
Run commands from docker/.
docker compose -f compose-single-sqlite.yml up --build— single node, SQLite, local filesystem blobs, local Tantivy.docker compose -f compose-postgres-s3-opensearch.yml up --build— cluster-ready application shape with PostgreSQL, SILO (S3-compatible blobs) and OpenSearch. The RustBox container has no persistentdata_dirvolume.NFS_SERVER=10.0.0.10 NFS_EXPORT=/exports/rustbox docker compose -f compose-mysql-nfs-opensearch.yml up --build— MySQL, real shared POSIX/NFS blob storage and OpenSearch.
Set IMAP_HOST and SMTP_HOST for the mail system. Replace all example passwords and SESSION_ENCRYPTION_KEY before production use. The OpenSearch examples disable its security plugin only to keep the local Compose topology self-contained; production should use TLS/authentication and search.urls with HTTPS.
The NFS variant deliberately uses an NFS volume driver instead of a local Docker named volume: a local named volume is not shared across Docker hosts and therefore is not a valid multi-node RustBox blob backend.
The two cluster-ready Compose examples intentionally run one RustBox application container so they remain directly runnable on a single Docker host. To run multiple RustBox application nodes, place them behind an external load balancer (or adapt the Compose networking) and do not publish the same host port from every node; the shared SQL/blob/OpenSearch services are the cluster-safe backing topology.