📋 Pre-flight Checks
🔍 Problem Description
It would be good if, during the Engram release process, a Docker image for Engram Cloud were published.
💡 Proposed Solution
In this way, docker-compose would be independent and there would be no need to have the Engram source code on the VPS.
services:
postgres:
image: postgres:16-alpine
container_name: engram-cloud-postgres
environment:
POSTGRES_USER: engram
POSTGRES_PASSWORD: engram_dev
POSTGRES_DB: engram_cloud
ports:
- "127.0.0.1:5433:5432"
healthcheck:
test: ["CMD-SHELL", "pg_isready -U engram -d engram_cloud"]
interval: 5s
timeout: 3s
retries: 10
volumes:
- engram-cloud-pg:/var/lib/postgresql/data
cloud:
image: gentleman/engram-cloud:0.0.1
container_name: engram-cloud
depends_on:
postgres:
condition: service_healthy
environment:
ENGRAM_DATABASE_URL: postgres://engram:engram_dev@postgres:5432/engram_cloud?sslmode=disable
ENGRAM_JWT_SECRET: engram-dev-jwt-secret-for-local-smoke-1234
ENGRAM_CLOUD_INSECURE_NO_AUTH: "1"
ENGRAM_CLOUD_ALLOWED_PROJECTS: smoke-project
ENGRAM_CLOUD_HOST: 0.0.0.0
ENGRAM_PORT: "18080"
ports:
- "127.0.0.1:18080:18080"
command: ["cloud", "serve"]
volumes:
engram-cloud-pg:
📦 Affected Area
Other
🔄 Alternatives Considered
No response
📎 Additional Context
No response
📋 Pre-flight Checks
status:approvedbefore a PR can be opened🔍 Problem Description
It would be good if, during the Engram release process, a Docker image for Engram Cloud were published.
💡 Proposed Solution
In this way, docker-compose would be independent and there would be no need to have the Engram source code on the VPS.
📦 Affected Area
Other
🔄 Alternatives Considered
No response
📎 Additional Context
No response