7dc634275e
Railway, DigitalOcean and `docker build` use a root Dockerfile with no setting, and it is Coolify's and Dokploy's default path. The file moves; nothing is copied. - VOLUME /data is gone. Railway rejects the line, and a named volume is needed anyway (VOLUME alone gives each new container a fresh anonymous one). The platforms mount /data. - The baked PocketBase gate's comment named the old path. It now says the repo-root Dockerfile, and the gate's SHA-256 pin moves with it (2987055b... -> 2eceef03...). The hook's code is unchanged: the exact RUN passes `sha256sum -c`, and the old block still passes its old pin. - .dockerignore excludes everything: the Dockerfile copies nothing from the build context, so no platform sends the whole repository to the builder. - compose.yaml: the same image with its /data volume and memory limit; settings from .env. - deployment/cloud/README.md gains "Where it runs": Coolify, Dokploy, Railway, a server with Docker, Kubernetes, and why not DigitalOcean App Platform (no persistent volumes). DEPLOY.md and two comments follow the move.
22 lines
751 B
YAML
22 lines
751 B
YAML
# One dx-maps team container, the same image a platform builds from ./Dockerfile:
|
|
# docker compose up -d --build
|
|
# Settings come from a .env file next to this one (never committed): REPO_URL is required, GIT_TOKEN
|
|
# for a private repo, and the OIDC_* settings for the sign-in; every setting is in deployment/cloud/README.md.
|
|
services:
|
|
dx-maps:
|
|
build: .
|
|
env_file:
|
|
- path: .env
|
|
required: false
|
|
environment:
|
|
REPO_URL: ${REPO_URL:?set REPO_URL to the dx-maps git URL, in .env}
|
|
BRANCH: ${BRANCH:-development}
|
|
PRODUCTION_BRANCH: ${PRODUCTION_BRANCH:-main}
|
|
ports:
|
|
- "${PORT:-5173}:${PORT:-5173}"
|
|
volumes:
|
|
- dx-data:/data
|
|
mem_limit: 2560m
|
|
restart: unless-stopped
|
|
volumes:
|
|
dx-data:
|