Match upstream Flood runtime while keeping torrent service separate

This commit is contained in:
k2patel committed 2026-09-30 21:18:06 -04:00
1 parent cb32b760a5
commit 8b6742f484
3 files changed
+10 -6

No files matched your search

+3 -3
View File
@@ -2,7 +2,7 @@
# Build from a clean upstream release checkout using the Gitea workflow. # Build from a clean upstream release checkout using the Gitea workflow.
ARG BUILDPLATFORM=amd64 ARG BUILDPLATFORM=amd64
ARG NODE_IMAGE=docker.io/node:24-alpine3.24 ARG NODE_IMAGE=docker.io/node:24.18.1-alpine3.24
FROM --platform=$BUILDPLATFORM ${NODE_IMAGE} as nodebuild FROM --platform=$BUILDPLATFORM ${NODE_IMAGE} as nodebuild
@@ -51,5 +51,5 @@ VOLUME /server/db/
# Fail the build before publication if the actual server cannot start. # Fail the build before publication if the actual server cannot start.
RUN node .ci-startup.cjs && rm .ci-startup.cjs RUN node .ci-startup.cjs && rm .ci-startup.cjs
# Flood server in development mode # Start Flood only, using the upstream v4.16.2 production entrypoint.
ENTRYPOINT ["npm", "--prefix=/usr/src/app/", "run", "start:development:server", "--", "--host=0.0.0.0", "--rundir=/server/"] ENTRYPOINT ["npm", "--prefix=/usr/src/app/", "run", "start", "--", "--host=0.0.0.0", "--rundir=/server/"]
+6 -2
View File
@@ -24,8 +24,12 @@ runner image store, and the temporary builder and cache are removed afterward.
No image archives or build records are uploaded to Gitea, and no local container No image archives or build records are uploaded to Gitea, and no local container
builds are required. builds are required.
Base image: Node.js 24 on Alpine Linux 3.24 stable (`node:24-alpine3.24`), Base image: Node.js 24.18.1 on Alpine Linux 3.24 stable (`node:24.18.1-alpine3.24`),
including the latest patch updates in those release series. with the Alpine stable series explicitly selected.
The image build starts the actual Flood server and requires HTTP 200 before The image build starts the actual Flood server and requires HTTP 200 before
publishing; it does not start a torrent daemon. publishing; it does not start a torrent daemon.
The entrypoint uses `npm run start`, matching upstream v4.16.2, while retaining
`--host=0.0.0.0` and `--rundir=/server/`. The upstream combined rTorrent stage
is deliberately excluded.
+1 -1
View File
@@ -4,7 +4,7 @@ const fs = require('node:fs');
const os = require('node:os'); const os = require('node:os');
const path = require('node:path'); const path = require('node:path');
const runDir = fs.mkdtempSync(path.join(os.tmpdir(), 'flood-smoke-')); const runDir = fs.mkdtempSync(path.join(os.tmpdir(), 'flood-smoke-'));
const child = spawn('npm', ['run', 'start:development:server', '--', const child = spawn('npm', ['run', 'start', '--',
'--host=127.0.0.1', '--port=3000', `--rundir=${runDir}`], '--host=127.0.0.1', '--port=3000', `--rundir=${runDir}`],
{stdio: 'inherit', detached: true}); {stdio: 'inherit', detached: true});
let startupError; let startupError;