feat: process municipal images through media pipeline
Deploy / validate-dispatch (push) Successful in 0s
Deploy / scheduled-rebuild-dev (push) Skipped
Deploy / scheduled-rebuild-master (push) Skipped
Deploy / rollback-dev (push) Skipped
Deploy / rollback-master (push) Skipped
Deploy / changes (push) Successful in 4s
Deploy / app-quality (push) Successful in 3m7s
Deploy / secret-scan (push) Successful in 5s
Deploy / security-deps (push) Successful in 6s
Deploy / context (push) Successful in 1s
Deploy / app-image (push) Successful in 55s
Deploy / deploy-master (push) Skipped
Deploy / deploy-dev (push) Successful in 12s

This commit is contained in:
Per Hoener
2026-09-19 16:52:07 +02:00
parent 775178f3f2
commit b50a172c1c
31 changed files with 43 additions and 29 deletions
+1 -1
View File
@@ -1,3 +1,3 @@
# Media sources
Store original project images in the matching subdirectories. The build pipeline derives optimized public variants from these files. Do not add production media, personal data, or unlicensed assets to the starter template.
Store original project images in the matching subdirectories. The Gitea CI/deployment pipeline derives responsive JPEG, WebP and AVIF variants from these files and places them under `public/images/`. Generated variants are intentionally not committed. Do not add production media, personal data, or unlicensed assets to the starter template.