bvandeusen/FabledCurator
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases 35 Wiki Activity
1,094 Commits 3 Branches 35 Tags
306de50f615e7254156dddd64ab5dd2bca021027
Commit Graph
7 Commits
Author SHA1 Message Date
Renovate Bot 6ab495292a chore(deps): update node.js to v24
renovate/stability-days Updates have met minimum release age requirement
Details
CI / lint (pull_request) Successful in 2s
Details
CI / frontend-build (pull_request) Successful in 16s
Details
CI / backend-lint-and-test (pull_request) Successful in 28s
Details
CI / integration (pull_request) Successful in 3m49s
Details
2026-07-12 01:33:07 +00:00
Renovate Bot e00deee451 chore(deps): update docker/dockerfile docker tag to v1.25
renovate/stability-days Updates have met minimum release age requirement
Details
2026-07-11 23:58:54 +00:00
bvandeusenandClaude Opus 4.8 bd2807cdd1 feat(external): mega.nz via megatools in the runtime image (Phase 4c)
CI / lint (push) Successful in 3s
Details
CI / backend-lint-and-test (push) Successful in 33s
Details
CI / frontend-build (push) Successful in 17s
Details
CI / integration (push) Successful in 3m17s
Details 
Use `megatools dl` (Debian-native apt package) for mega.nz public links rather
than MEGAcmd — no external MEGA apt repo/key to add, one apt line. Adds
`megatools` to the runtime Dockerfile; the fetcher's mega backend now shells
`megatools dl --path <dir> <url>` (key in the #fragment is preserved by the
extractor). gdown (gdrive) is already a pip dep in the runtime image.

NOTE: build.yml builds the image on main/tags only (not dev), so this Dockerfile
change is verified on the next dev→main merge, not by this dev push. The fetcher
code path is unit-tested via the mocked _run_mega_get seam.

With this, all 5 hosts download end-to-end once a celery download-worker runs.
Refs FC #830 (Phase 4c).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-06-14 15:41:18 -04:00
bvandeusenandClaude Opus 4.7 7f26217166 fc5: install postgresql-client + zstd in runtime image so backup/rollback work 
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-22 22:17:18 -04:00
bvandeusenandClaude Opus 4.7 aa9705882f fix: use npm install in Dockerfile frontend-builder stage (no lockfile) 
Same fix as the CI workflow — `npm ci` requires package-lock.json and we
don't track one. Missed this in the earlier CI fix. Local `docker compose
up` builds now succeed past the frontend stage.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-14 21:01:29 -04:00
bvandeusenandClaude Opus 4.7 37e97d52ee chore: bump runtime targets to Python 3.14 and Node 22 
Forward-looking pin per operator direction ("build for the future and not
rebuild the past"). Touches everywhere a version is named so all
downstream artifacts (Dockerfiles, ruff config, package.json engines)
agree.

Python 3.14 (released Oct 2025) is the current stable. Node 22 is the
most recent LTS line still receiving updates (Maintenance LTS since
Oct 2025); Node 24 (released Apr 2026) goes Active LTS in Oct 2026 and
will be the natural next bump.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-14 07:52:15 -04:00
bvandeusenandClaude Opus 4.7 1db0167bfc feat: add Dockerfile for web/worker/scheduler roles and entrypoint script 
Multi-stage build: node:20 builds the SPA, python:3.12-slim runs the app.
Same image handles web, worker, scheduler roles via entrypoint.sh's first
arg. ffmpeg + unar are baked in for FC-2's transcode + archive paths.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-14 07:42:04 -04:00