Skip to content

feat(umami): add Umami analytics installer - #1

Open
KartikJain14 wants to merge 1 commit into
excloud-dev:mainfrom
KartikJain14:feat/umami-example
Open

feat(umami): add Umami analytics installer#1
KartikJain14 wants to merge 1 commit into
excloud-dev:mainfrom
KartikJain14:feat/umami-example

Conversation

@KartikJain14

Copy link
Copy Markdown

What

Adds Umami (privacy-friendly, self-hosted web analytics) as a new app example.

How

Follows the existing catalog convention — install.sh + domain.sh on top of the shared _common/caddy-setup.sh flow, matching self-contained apps like nocodb / open-webui:

  • Self-contained deployment: Umami app + PostgreSQL 16 (inline docker-compose.yml).
  • App bound to 127.0.0.1:3000; Caddy fronts it over HTTPS with the standard initializing → reverse-proxy switch.
  • APP_SECRET and the DB password are generated once (openssl rand) and persisted to .app_secret / .database_password, so re-runs stay stable and don't invalidate sessions.
  • domain.sh has nothing to rewrite (Umami reads no host/base-URL env), so it just points Caddy at the running container.

Notes for reviewers

  • Image pinned to ghcr.io/umami-software/umami:postgresql-v2.19.0 — please confirm this is the desired tag before merge.
  • Umami ships a default admin login (admin / umami); the README calls out changing it on first login.
  • Not yet run end-to-end on a live VM (needs root + /var/excloud + Docker) — happy to adjust after a test deploy.

Self-contained install (Umami app + PostgreSQL 16) following the standard
install.sh/domain.sh + shared caddy-setup pattern. App bound to
127.0.0.1:3000 and fronted by Caddy over HTTPS. APP_SECRET and DB password
are generated once and persisted across re-runs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant