ci: build the production image in CI
Dokploy built from source on the host, so every deploy paid a full cold cargo build and the layer cache died with the builder. CI now builds and pushes to the Gitea registry, and the deploy is a pull. The Gitea push webhook fires before Actions starts, so autoDeploy on the Dokploy application is off and this job triggers the deploy itself. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
4d347cd285
commit
a9848fddce
+25
-7
@@ -8,17 +8,35 @@ RUN pnpm -C web install --frozen-lockfile --config.dangerouslyAllowAllBuilds=tru
|
||||
COPY web ./web
|
||||
RUN pnpm -C web build
|
||||
|
||||
FROM rust:1-bookworm AS build
|
||||
# Every translation backend is a default-off cargo feature (DESIGN.md §15), so
|
||||
# a build without these ships an image that cannot translate at all. All four
|
||||
# go in: which one is in use is a database setting, and the point of the
|
||||
# feature switches is the build, not the deployment.
|
||||
#
|
||||
# The dependency build and the workspace build are split with cargo-chef so a
|
||||
# source-only change reuses the dependency layer. The two `cargo` invocations
|
||||
# must carry identical flags or the cook output is not reusable.
|
||||
FROM lukemathwalker/cargo-chef:latest-rust-1-bookworm AS chef
|
||||
WORKDIR /src
|
||||
ENV ARR_FEATURES=translate-openai,translate-deepl,translate-google,translate-command
|
||||
|
||||
FROM chef AS planner
|
||||
COPY . .
|
||||
RUN cargo chef prepare --recipe-path recipe.json
|
||||
|
||||
FROM chef AS build
|
||||
COPY --from=planner /src/recipe.json recipe.json
|
||||
# cargo-chef's skeleton keeps build scripts, and arr-daemon's panics in release
|
||||
# when it can find no SPA bundle. A stub satisfies it; the real bundle arrives
|
||||
# below and the changed ARR_WEB_DIST reruns only that one build script.
|
||||
RUN mkdir -p /stub/dist && printf '<!doctype html>stub\n' > /stub/dist/index.html
|
||||
ENV ARR_WEB_DIST=/stub/dist
|
||||
RUN cargo chef cook --release -p arr-daemon --features "$ARR_FEATURES" \
|
||||
--recipe-path recipe.json
|
||||
COPY . .
|
||||
COPY --from=web /src/web/dist ./web/dist
|
||||
ENV ARR_WEB_DIST=/src/web/dist
|
||||
# Every translation backend is a default-off cargo feature (DESIGN.md §15),
|
||||
# so a build without this line ships an image that cannot translate at all.
|
||||
# All four go in: which one is in use is a database setting, and the point of
|
||||
# the feature switches is the build, not the deployment.
|
||||
RUN cargo build --release -p arr-daemon \
|
||||
--features translate-openai,translate-deepl,translate-google,translate-command
|
||||
RUN cargo build --release -p arr-daemon --features "$ARR_FEATURES"
|
||||
|
||||
# §15 runs `alass` over every fetched and every translated subtitle, and it is
|
||||
# not in Debian — a release binary is the only way in. Its own stage so the
|
||||
|
||||
Reference in New Issue
Block a user