peter 636372511b chore: remove the unreferenced backend/Dockerfile ...

Nothing builds from it: both compose files build the root Dockerfile, and the
test image has its own Dockerfile.test. It installed the unpinned
requirements.txt, contradicting the lock header that every image installs
requirements.lock.

2026-09-13 23:12:16 +02:00

..

alembic

feat(downloads): a per-site failure catalog — Facebook's walls say why and what to do

2026-09-13 21:53:25 +02:00

app

feat(downloads): a Facebook cookie download stuck at "Cannot parse data" is retried as Chrome

2026-09-13 22:48:21 +02:00

tests

feat(downloads): a Facebook cookie download stuck at "Cannot parse data" is retried as Chrome

2026-09-13 22:48:21 +02:00

alembic.ini

feat: M1 foundation — compose stack, FastAPI, Google OAuth, encrypted tokens

2026-06-11 01:01:37 +02:00

docker-compose.test.yml

test(infra): fail-loud DB/ffmpeg lane + client/as_user/make_user fixtures (E1 S2, TEST-4)

2026-08-18 01:23:06 +02:00

Dockerfile.test

build(deps): pin a reproducible lock + pip-audit; bump node 20->22 (E1 S4, SEC-5/DX-3)

2026-08-18 02:34:45 +02:00

entrypoint.sh

harden(auth): SA3 review follow-ups — IPv6-mapped match + no-proxy-headers guardrail

2026-07-12 03:49:08 +02:00

log_config.json

chore: rename remaining subfeed references to siftlode

2026-06-21 06:53:12 +02:00

pytest.ini

test(infra): fail-loud DB/ffmpeg lane + client/as_user/make_user fixtures (E1 S2, TEST-4)

2026-08-18 01:23:06 +02:00

requirements-dev.txt

test(backend): pin the traversal guard against a string-prefix bypass

2026-07-21 03:36:42 +02:00

requirements.lock

feat(downloads): a Facebook cookie download stuck at "Cannot parse data" is retried as Chrome

2026-09-13 22:48:21 +02:00

requirements.txt

feat(downloads): a Facebook cookie download stuck at "Cannot parse data" is retried as Chrome

2026-09-13 22:48:21 +02:00

ruff.toml

chore(lint): set ruff line-length 100 and gate ruff format --check

2026-08-23 07:42:42 +02:00