.dockerignore

README_images
docker-compose.yml
.git
.github
.gitignore
.github/workflows
.gitattributes
.po~
build.sh
README.md
LICENSE
Dockerfile
.dockerignore
build.sh
.history
docker-compose.yml.dev
changelogs
cwa-wiki
wiki_images
.devcontainer
.editorconfig
AI_README.md
babel.cfg
changelog.d
CHANGELOG.md
CHANGES-vs-upstream.md
CONTRIBUTING.md
CONTRIBUTORS
docs
drafts
examples
feedback-server
findings
GOVERNANCE.md
greptile.json
homepage
kubernetes
messages.pot
notes
run_tests.sh
SECURITY.md
state
wiki-src
wikisite

# Test infrastructure (not needed in production image). Dev dependencies now
# live in pyproject.toml's [project.optional-dependencies].dev extra, which the
# image must keep (STEP 3 installs from it), so there is no dev requirements
# file left to exclude here.
tests/
pytest.ini
TEST*.md
TESTING*.md
.pytest_cache/

# Frontend: node_modules is reinstalled in the frontend-build stage via
# `npm ci`; the compiled bundle is produced there and COPY'd in, so a local
# build must never leak into the context (keeps builds reproducible + lean).
frontend/node_modules
cps/static/app/

# Runtime state must never be baked into the image. A developer who mounts
# /config at the repo root (the documented local-dev setup) otherwise ships
# their own .cwa_migrations markers inside the build — and a marker present on
# a fresh install makes the migration it gates get *skipped*, so the install
# silently never runs it. CI builds from a clean checkout and was never
# affected; local images were (#1162).
.cwa_migrations/
# Same reasoning for the metadata enforcement dirs (#995): they resolve under
# CONFIG_DIR, which outside a container is the repo root, and cwa-init now
# migrates anything left in the old location into the user's /config. A change
# log baked into the image would be enforced onto whatever real book shares its
# id on someone else's install.
metadata_change_logs/
metadata_temp/
app.db
*.db-wal
*.db-shm

# Raw Kobo exchange diagnostics and PATCH recovery bodies can contain private
# annotation text when a bare source run uses the checkout as CONFIG_DIR.
.cwng-private-observability/

# Local developer artifacts. All four are git-ignored, so a CI checkout never
# has them and published images were never affected -- but a local `docker
# build` copied them straight into /app/calibre-web-automated/. Measured with a
# `FROM scratch` + `COPY . /` probe, excluding just these four took the copied
# layer from 299,311,528 to 17,832,889 bytes -- 281 MB. Same class as the .cwa_migrations note
# above: a developer's tree must not end up inside the image.
.venv
.claude
.coverage
calibre-web.log

# Local development stacks and the KOReader emulator. Nothing here is COPY'd
# into the image, and the emulator's default KOEMU_HOME writes a KOReader home
# and book library under local-dev/ -- which would otherwise be uploaded as
# build context on every local image build.
local-dev/