Skip to content

Release: run the app with Docker, and move .env to the repo root - #56

Merged
amide-init merged 5 commits into
mainfrom
dev
Oct 9, 2026
Merged

amide-init merged 5 commits into
mainfrom
dev

Conversation

@amide-init

Copy link
Copy Markdown
Owner

Brings #55 from dev to main.

Included

  • Run the app with Docker, and move .env to the repo root #55 Run the app with Docker, and move .env to the repo root
    • Dockerfile + compose.yaml: one container on 127.0.0.1:3001 with Bun, static FFmpeg 9.0.2 (libass) and caption fonts, data in a transcriptcut-data volume
    • one root .env (moved from server/.env) shared by pnpm run dev, the Prisma CLI and compose
    • docs lead with Docker; scripts/setup-mac.sh removed

After merging

  • Existing checkouts: mv server/.env .env.
  • The docs deploy runs, since docs/** changed.

Testing

CI runs on this PR. That's the first CI run for these changes, since CI only runs on PRs to main.

🤖 Generated with Claude Code

amide-init and others added 5 commits October 9, 2026 05:58
The setup steps work the same on every platform (pnpm install, copy
.env, prisma generate), so a separate macOS-only script to maintain
isn't worth it. The docs now have one setup path, starting from git
clone, which the script's section used to carry. The useful part of
the script, catching an FFmpeg build without libass, is still covered
by the FFMPEG_PATH note in server/.env.example.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Running the app meant installing Node, pnpm, Bun and an FFmpeg build
with libass by hand. The image does that once: a Node stage builds the
client and a production-only server, and an oven/bun runtime serves both
from one port with data under a /data volume. Startup migrations turn an
empty volume into a working database, so no Prisma CLI is needed.

FFmpeg is the static 9.0.2 build (libass included, and the version the
xfade workarounds in plan.ts were measured on), not Debian's 5.1.
Caption and card fonts are Liberation + DejaVu stand-ins rather than
Microsoft's core fonts, which would be a build-time download with
licensing caveats. compose publishes on 127.0.0.1 only, since the app
has no login.

Also drops better-sqlite3 from onlyBuiltDependencies: it's only an
optional peer of the Prisma CLI (the app uses adapter-libsql), and its
native build fails noisily in a container without Python.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Docker is now the documented way to run the app; the pnpm setup stays
as the development setup for contributors. Covers the API key (setup
screen or .env), where data lives, how to update, the localhost-only
port and why caption fonts can differ from a Mac.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With Docker, compose reads .env from the repo root while the dev server
read server/.env, so running both meant keeping two files in sync. Now
there's one root .env for both. The dev server loads it with
bun --env-file=../.env, since Bun's own loading only looks in the
working directory (server/). prisma7.config.ts loads it too, which also
fixes the Prisma CLI: it never read server/.env, so migrate commands
failed for lack of DATABASE_URL.

compose now pins the container's paths, port and FFmpeg binaries over
the env file, because dev values in it (relative paths, a Homebrew
FFMPEG_PATH) don't exist inside the container. In .env.example only
OPENAI_API_KEY is left uncommented; the rest match the code's defaults.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Run the app with Docker, and move .env to the repo root
@amide-init
amide-init merged commit 83d87c8 into main Oct 9, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant