polylan/polylan-submitter
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: deployment move to docker only

Browse Source
This commit is contained in:
Legrems
2026-09-19 13:36:48 +02:00
parent 59b568ff41
commit b74d20cbe0
11 changed files with 68 additions and 257 deletions
Download Patch File Download Diff File Expand all files Collapse all files
deploy/docker/README.md
+13 -11
View File
@@ -9,12 +9,11 @@ one container:
- `worker` - two `rqworker` processes for background jobs (submission OCR,
AAndT sync, etc.)
Postgres, Redis and S3-compatible storage are **not** bundled - the image
expects them the same way the bare-metal deploy does (see
`deploy/supervisor/polylan-submitter.env.dist` for the full list of env
vars: `POSTGRES_*`, `REDIS_HOST`/`REDIS_PORT`, `AWS_*`, `DJANGO_SECRET_KEY`,
etc.). Point those at wherever those services already live (other
containers/LXCs, or existing infra).
Postgres, Redis and S3-compatible storage are **not** bundled (see
`deploy/docker/polylan-submitter.env.dist` for the full list of env vars:
`POSTGRES_*`, `REDIS_HOST`/`REDIS_PORT`, `AWS_*`, `DJANGO_SECRET_KEY`, etc.).
Point those at wherever those services already live (other containers/LXCs,
or existing infra).
## Build
@@ -30,7 +29,7 @@ docker buildx build --load -t polylan-submitter .
```sh
docker run -d \
--name polylan-submitter \
--env-file deploy/supervisor/polylan-submitter.env \
--env-file deploy/docker/polylan-submitter.env \
-p 8000:8000 \
polylan-submitter
```
@@ -41,15 +40,18 @@ shared S3 bucket, so run it once per deploy instead of racing multiple
replicas on every boot:
```sh
docker run --rm --env-file deploy/supervisor/polylan-submitter.env \
docker run --rm --env-file deploy/docker/polylan-submitter.env \
polylan-submitter python manage.py collectstatic --noinput
```
## Scaling
There's one `daphne` process per container (unlike the bare-metal deploy's
`NUM_WEB_WORKERS` behind HAProxy) - scale by running multiple container
replicas behind an external reverse proxy/load balancer instead.
There's one `daphne` process per container - it binds the only port the
container exposes, so running more of them would need a reverse proxy
inside the container too. Scale by running multiple container replicas
behind an external reverse proxy/load balancer instead (each replica also
runs its own pair of `rqworker` processes, so worker capacity scales the
same way).
## Deploying to Proxmox