Commit Graph
9 Commits
Author SHA1 Message Date
SluijsensandClaude Sonnet 5 3af15159fe Consistente _TEST/_PRODUCTION postfix voor omgevingsspecifieke Gitea variables
Continuous Integration / config (pull_request) Successful in 10s
Continuous Integration / prepare (pull_request) Successful in 1m14s
Continuous Integration / build-production (pull_request) Skipped
Continuous Integration / build (pull_request) Successful in 1m56s
Continuous Integration / test (pull_request) Successful in 1m48s
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / deploy-production (pull_request) Skipped
Hernoemt de Gitea-variable achter VITE_UMAMI_WEBSITE_ID naar
VITE_UMAMI_WEBSITE_ID_TEST, zodat deze consistent is met
VITE_UMAMI_WEBSITE_ID_PRODUCTION en DEPLOY_PATH_TEST/DEPLOY_PATH_PRODUCTION.
De Vite build-time envvar-naam die de app zelf verwacht
(VITE_UMAMI_WEBSITE_ID) verandert niet, alleen de naam van de Gitea
repository variable erachter. Bewust gedeelde variabelen (VITE_UMAMI_SCRIPT_URL,
VITE_SENTRY_DSN, PI_MAIN_* secrets) krijgen geen postfix, want die zijn
geen omgevingsspecifieke waarden. Documentatie in umami-setup.md,
deployment-instructions.md en monitoring-plan.md bijgewerkt.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-27 12:16:10 +02:00
SluijsensandClaude Sonnet 5 4bddcbbc50 Splits Umami website-ID per omgeving in productie-build (was per ongeluk gedeeld)
build-production hergebruikte vars.VITE_UMAMI_WEBSITE_ID van de testbuild,
maar Umami-website-ID's horen bij één specifieke domeinentry in het
dashboard. Zonder deze fix zou productieverkeer in de teststatistieken
terechtkomen. Introduceert VITE_UMAMI_WEBSITE_ID_PRODUCTION als losse Gitea
variable, en documenteert dat er twee aparte Umami-website-entries nodig
zijn (test.slpsoftware.nl / slpsoftware.nl). VITE_UMAMI_SCRIPT_URL en
VITE_SENTRY_DSN blijven bewust gedeeld tussen omgevingen.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-27 12:12:13 +02:00
Sluijsens d71d0636c0 Split nginx voorbeeldconfigs in pre- en post-certbot varianten, plus access/error logs
Continuous Integration / config (pull_request) Successful in 10s
Continuous Integration / prepare (pull_request) Successful in 1m13s
Continuous Integration / build (pull_request) Successful in 2m2s
Continuous Integration / test (pull_request) Successful in 1m51s
Continuous Integration / deploy-test (pull_request) Skipped
De reverse-proxy en analytics nginx-configs toonden al de door certbot beheerde
eindstaat (met SSL-directives), terwijl je die juist nodig hebt vóórdat certbot
draait. Nu is het .example-bestand de kale HTTP-versie om te kopiëren, met een
apart .post-certbot.example ter referentie voor de staat erna. Alle configs
(inclusief webserver-nginx.conf.example) hebben nu ook expliciete error_log/
access_log directives.
2026-07-25 23:45:34 +02:00
SluijsensandJunie 61fc6ba4c4 Document fix for 'Failed to connect to bus' when setting up Umami systemd user service
Co-authored-by: Junie <junie@jetbrains.com>
2026-07-25 23:22:06 +02:00
SluijsensandJunie 00a80cccbb Document ufw rule needed for Umami port 3001 (fixes connection reset by peer)
Co-authored-by: Junie <junie@jetbrains.com>
2026-07-25 23:15:15 +02:00
SluijsensandJunie 3ec22f4b9e Explain podman-compose down/up needed after config changes to existing container
Co-authored-by: Junie <junie@jetbrains.com>
2026-07-25 23:00:40 +02:00
SluijsensandJunie 11b77a6994 fix: change Umami external port from 3000 to 3001 to avoid conflict with Gitea
Co-authored-by: Junie <junie@jetbrains.com>
2026-07-25 22:53:34 +02:00
SluijsensandJunie 5102945ab4 Umami self-hosted setup: draai onder eigen dedicated user i.p.v. hoofdaccount
Co-authored-by: Junie <junie@jetbrains.com>
2026-07-25 21:37:14 +02:00
SluijsensandJunie 08b489e305 Voeg self-hosted Umami analytics + UptimeRobot uptime dashboard toe
Co-authored-by: Junie <junie@jetbrains.com>
2026-07-25 19:59:40 +02:00