Skip to content

Tidemark Analytics 0.38.3

Choose a tag to compare

@github-actions github-actions released this 10 Nov 01:09
· 15 commits to main since this release
1eadad7

Added

  • A host that runs Tidemark for other people can set an install's plan with a JSON file (TIDEMARK_PLAN_FILE): how many sites and events a month it includes, whether recording stops at that limit, which features (alerts, branding, funnels, revenue, segments, journeys, campaign links, rollups) are on, whether personal data is always masked, and whether the install is paused. Changing the file applies on the next request, and a missing or broken file limits nothing. php artisan tidemark:usage prints this month's events and the sites against the plan (--json for scripts).
  • php artisan tidemark:provision you@example.com sets up a fresh install without the web installer: it creates the database tables and the owner account, and prints a one-time link for choosing a password (--hours sets how long it works, --json prints it for scripts). Run it again to get a new link.
  • Set TIDEMARK_ORGANIZATIONS=false to turn organizations off, for an install that serves a single customer. The organization switcher, the Organization and Teams settings and "Move to another organization" disappear, every site you can open is listed together, and sites are still shared with people one by one. Everything stays on as before unless you set it.
  • php artisan tidemark:usage also reports the number of users, when the last event arrived, the size of the SQLite database file and the installed version, so a host can monitor an install without opening it.
  • With TIDEMARK_HOSTED=true the app no longer points people at the environment file: where outgoing email isn't working, Email reports says to contact support. Outgoing email itself is only ever set in the environment, so a host controls it and nothing in the app can change it.
  • When the plan file stops recording (the account is paused, or this month's events are used up and the plan has a hard limit) a red banner across the app says so, with the date recording resumes.
  • A host that runs Tidemark for other people can sign its customers in, and its support staff, with a short-lived signed link (/sso), once TIDEMARK_SSO_PUBLIC_KEY is set. A support link opens the account for a limited time (60 minutes at most) in a read-only session: it can look but not change anything, a red banner says so, and Security → Support access lists who looked, why and when. Set TIDEMARK_SUPPORT_ACCESS=false to refuse support links. Nothing changes if no key is set.