feat: add docker support#268
Conversation
|
I came across this repo from an LinkedIn post and was wondering to to run it locally. While I was struggling to find a Dockerfile I was not able to find it. Thought of adding it but then looked at your PR! |
|
I was also looking for a containerized version of this software and stumbled upon this pull request. It was indeed as simple as running This pull request actually offers two things:
Already having a container image that builds automatically with each commit and is automatically pushed as release with each official release is a huge win already. Where possibly an example of the |
|
Keeping this open as the Docker track, but the current 11-line image is a development proof rather than a production container. A current-main revision should verify the GitHub package dependency installs on Alpine, use a multi-stage build with a non-root runtime, copy only runtime output/dependencies, add a healthcheck, and document required build/runtime env. Please include the exact docker build and run commands plus an /api/health result. That evidence will also let us decide whether Next standalone output is worth enabling. |
Summary
Dockerfileusingoven/bun:1.3.0-alpinethat installs dependencies, builds all workspace packages via Turbo, and serves the Next.js appdocker-compose.ymlfor a one-command start (docker compose up --build).dockerignoreto excludenode_modules, build artifacts, and local env files from the build contextUsage
The editor will be available at
http://localhost:3000.Optional env vars (e.g.
NEXT_PUBLIC_GOOGLE_MAPS_API_KEY) can be passed under theenvironmentkey indocker-compose.yml— the editor works without them.Test plan
docker compose up --buildcompletes without errorshttp://localhost:3000