Root README reports Angular 19, Spring Boot 3, and a .env.local chain Compose does not load #111

What is wrong

The root README describes this stack as Angular 19 and Spring Boot 3. The admin and viewer apps depend on Angular 22, and the four Gradle modules pin Spring Boot 4.1.1.

The same README says Docker Compose loads .env, then .env.local, then the process environment. Compose loads .env for interpolation. A .env.local file in the project directory is ignored unless it is passed with --env-file.

Where

Angular 19 and Spring Boot 3 are stated in README.md at lines 38-39, 42-43, 55-58, 63-64, 571-577, and 1227-1228. Line 577 includes MBTiles in the Spring Boot 3 claim.

Current pins:

• front/admin/sitmun-admin-app/package.json line 32: @angular/core ^22.2.3
• front/viewer/sitmun-viewer-app/package.json line 38: @angular/core ^22.2.3
• spring-boot = "4.1.1" in back/backend/sitmun-backend-core/gradle/libs.versions.toml line 3, back/proxy/sitmun-proxy-middleware/gradle/libs.versions.toml line 3, back/mbtiles/sitmun-mbtiles/gradle/libs.versions.toml line 3, and back/shared/sitmun-shared/gradle/libs.versions.toml line 2

The .env.local claim is README.md line 112. docker-compose.yml lines 21-22 and 36-38 repeat it. No compose service sets env_file to .env.local.

Checked with Docker Compose v5.6.1. A project with FOO=from-dotenv in .env and FOO=from-local in .env.local interpolated from-dotenv from docker compose config. The same project with --env-file .env --env-file .env.local interpolated from-local.

Why it matters

A reader targets the wrong framework versions. An override written to .env.local, as the quick start describes, does not change the Compose project.

Smallest fix

Replace the Angular 19 and Spring Boot 3 lines with Angular 22 and Spring Boot 4.1.1. Drop the .env.local load order, or document docker compose --env-file .env --env-file .env.local if that override should keep working.