.dockerignore

# AUTO-GENERATED from .gitignore by 'mise run gen:dockerignore' -- do not edit.
# Docker reads only this file; patterns are **/-prefixed to match at any depth
# like .gitignore. Edit .gitignore and regenerate.

# `.dockerignore` is generated from `.gitignore` by `mise run gen:dockerignore`.
# After editing `.gitignore`, regenerate it and commit both, or the dockerignore-check task fails on drift.
**/.claude/
**/*.wasm
**/*.onnx
**/target/
**/.DS_Store
services/ws-wasm-agent/pkg/
services/ws-modules/pywasm1/pkg/
services/ws-modules/rdata1/pkg/webr/
services/ws-modules/rcomm1/pkg/webr/
services/ws-modules/rmath1/pkg/webr/
services/ws-modules/js-data1/pkg/et_ws_js_data1.js
services/ws-server/static/models/
**/.zig-cache/
**/zig-out/
**/*.o
**/*.pem
**/mprocs.log
**/__pycache__/
**/.pytest_cache/
**/.python-version
**/node_modules/
**/.venv/
# .NET build output.
# `obj/` is safe globally (nothing tracked is named obj/), but `bin/` is scoped to the module so it never
# matches a Rust crate's `src/bin/` (e.g. utilities/int-gen/src/bin/).
**/obj/
services/ws-modules/dotnet-data1/bin/
# Gradle project caches and build output plus the Kotlin session dir, all regenerated by any Gradle run.
**/.gradle/
**/.kotlin/
services/ws-modules/kotlin-data1/build/
services/ws-modules/kotlin-math1/build/
# Coverage-report artifacts produced by the coverage workflow, uploaded to Codecov and never committed.
# Covers cargo-llvm-cov's lcov, pytest-cov's Cobertura xml, and pytest-cov's .coverage data file.
lcov.info
**/coverage-python.xml
**/.coverage
# minicov/llvm raw profiles dropped by instrumented binaries run during coverage builds.
**/*.profraw
# Editor dir, tool caches, and the ws-server's runtime file storage.
# The .vscode dir is ignored except its shared recommended-extensions list (negated below).
.vscode/*
!.vscode/extensions.json
**/.ruff_cache/
**/.lycheecache
# Dart pub tool dir, regenerated by `dart pub get`; one global rule for the whole workspace (root + members).
**/.dart_tool/
services/ws-server/storage/
# No rule for the per-scenario credential file, deliberately.
# Under verification/ it is committed like every other generated artifact: the password is derived from an
# input this repository already carries, so the file reproduces from public material rather than keeping a
# secret, and the drift check has to be able to read it. A deployment generated anywhere else gets its own
# `.gitignore` written beside it by `et-cli`, which is what keeps a real credential out of a real repository.
**/.git/
**/Dockerfile*
README.md