28 driver application.yml add dc3.driver.buffer; Dockerfile each stage adds dc3/data dir and VOLUME; docker-compose main/dev add driver_data named volume
The 20 driver targets (bacnet-ip .. zigbee) were each defined twice in
the root Dockerfile (54 FROM stages, 34 unique). BuildKit used the later
copy, so builds worked, but editing one copy and missing the other could
silently produce wrong images. Drop the duplicate block (-261 lines).
Verified all 34 targets still resolve via `podman build --target`.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* ci(dependabot): add cargo ecosystem, groups, and clean up stale docker directories
* docs(ai): add spring-ai-deep-dive cross-references in en and zh indexes
* docs(community): add english FAQ and frontend developer guide
* chore(issue-templates): translate all templates to english
* ci(docker): add 20 missing driver images to Dockerfile, compose, and Makefile
* fix(docs): remove Vue template syntax from panorama SVGs so they render
* docs(ai): add spring-ai-deep-dive pages in en and zh
Parametrize JDK/JRE base images via build args in Dockerfile, replace
hardcoded GC/dump env vars with per-service path variables, fix APM
port. Simplify Makefile registry options to global|cn, add SERVICES
and GROUP selectors for targeted compose operations.
Replace 14 individual Dockerfiles with a single unified Dockerfile at
the repo root using multi-stage BuildKit targets. Maven build runs
inside the builder stage so no host JDK is required.
Reordered the `WORKDIR` and `RUN` commands in multiple Dockerfiles to ensure a more logical and consistent structure. This improves readability and maintainability of the Dockerfiles.
Consolidated Dockerfile configurations by removing redundant build steps and updated CI workflows to use consistent naming conventions. This improves maintainability and reduces complexity in the build process.
Updated the version from 2025.2.4 to 2025.2.5 in pom.xml files and various Java classes to reflect the latest release. This change ensures consistency across the codebase and aligns with the new version of the IoT DC3 Platform.