zeekay
eb9a9887d0
- Replace @umami/* imports with @hanzo/* npm aliases in package.json - Rename redis client to KVClient (UmamiRedisClient as KVClient) - Rename collector/forward/umami.go → analytics.go (git mv) - Remove all umami backwards-compat aliases from tracker (data-umami-event, window.umami, umami.disabled localStorage, eventNameAttributeLegacy) - Purge 93 umami. prefixes from ClickHouse SQL migrations - Update default admin password hash from "umami" to "analytics" - Rebrand podman service files, GitHub Actions, telemetry URL, seed scripts - Add data-test attributes to WebsiteAddButton, WebsitesTable, UserAddForm, UserEditForm for Cypress test compatibility - Refactor UsersTable: replace MenuButton portal dropdown with inline LinkButton (edit) + Button (delete) so Cypress .within() can find them - Fix Cypress tests: update selectors (td[label] → cy.contains), remove stale tab-navigation (settings page is vertical, not tabbed), scope button[type=submit] to [role=dialog] for delete confirmation - All 34 Cypress e2e tests now pass (was 28/34)
1.3 KiB
How to deploy Hanzo Analytics on podman
How to use
- Rename
env.sampleto.env - Edit
.envfile. At the minimum set the passwords. - Start analytics by running
podman-compose up -d.
If you need to stop analytics, you can do so by running podman-compose down.
Install systemd service (optional)
If you want to install a systemd service to run analytics, you can use the provided systemd service.
Edit analytics.service and change these two variables:
WorkingDirectory=/opt/apps/analytics
EnvironmentFile=/opt/apps/analytics/.env
WorkingDirectory should be changed to the path in which podman-compose.yml
is located.
EnvironmentFile should be changed to the path in which your .envfile is
located.
You can run the script install-systemd-user-service to install the systemd
service under the current user.
./install-systemd-user-service
Note: this script will enable the service and also start it. So it will assume that analytics is not currently running. If you started it previously, bring it down using:
podman-compose down
Compatibility
These files should be compatible with podman 4.3+.
I have tested this on Debian GNU/Linux 12 (bookworm) and with the podman that is distributed with the official Debian stable mirrors (podman v4.3.1+ds1-8+deb12u1, podman-compose v1.0.3-3).