zeekay
04314dabdc
The route tree moves from src/app/api to src/app/v1, and every caller moves with it: the dashboard's useApi base, the tracker and recorder collect paths, the Next headers and rewrites, the container middleware, the compose healthchecks and the Cypress API tests. The /v1/analytics alias is gone; /v1 is the one prefix. The build-time telemetry post to an upstream endpoint nothing serves is deleted. v1-surface.test.ts fails if src/app/api returns or any first-party file names an /api/ path. Claude-Session: https://claude.ai/code/session_011i2AG9nwpiKUCVxAdDzYuU
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).