10 Commits

Include renames

Author	SHA1	Message	Date
mrhid6	f4f41e400b	feat: public status page	2026-08-24 14:53:42 +00:00
mrhid6	7e767ecb4f	fix: Move the API keys page off the /api prefix ... /api-keys shares a raw string prefix with /api, and the proxies in front of this app do not all match by path segment. Nginx Proxy Manager routes /api straight to the Go server with a prefix location, so /api-keys never reached Next at all — it reached a control plane with no such route and came back as a JSON 404. Traefik's PathPrefix has the same shape of matcher, which puts the Helm ingress at risk whenever ingress.api.enabled is on. The page is /tokens now, which cannot collide with anything, and which matches the /api/tokens the REST API already publishes. The sidebar still says API Keys — the label is for the reader, the path is for the router. A permanent redirect covers anyone who bookmarked the old path today. Fixing the proxy config instead would have left the trap set for the next deployment, and for whatever sits in front of it.	2026-08-13 09:26:34 +00:00
mrhid6	487de34a50	docs: Updated docs	2026-07-28 16:53:42 +01:00
mrhid6	5be9ddb2e5	fix: Fixed baked api url	2026-07-28 16:18:50 +01:00
mrhid6	653bd5a755	refactor(web): members and SSO move onto the settings page ... /settings/instance held two cards — Members and Single sign-on — behind a sidebar entry called "Instance", next to one called "Settings". Nothing in either name told you which held what, and the split left both pages thin. They are now the Access group at the top of /settings, above Monitoring and Integrations. Six cards on one page needs sorting into groups or it reads as a pile, so each group carries site/'s keyed-label eyebrow on a hairline. The cards move to web/components/settings/ rather than into the page, which would have made it ~600 lines. That is also where the Field and inputClass pair now lives: the two pages each had a byte-identical copy, and folding them together is exactly when three copies would have started to drift. Members and SSO adopt SectionCard, which the rest of the page already used. A card that kept its own header treatment would read as a different kind of thing rather than another setting, which is the problem being fixed. next.config.ts keeps a permanent redirect from the old path, so bookmarks and any support reply linking it still land somewhere useful.	2026-07-26 20:19:04 +01:00
mrhid6	d31486ae1b	fix: Fixed agent windows version	2026-07-17 15:38:00 +01:00
mrhid6	bf96dba50e	fix: Fixed install ps1 script handler	2026-07-17 14:45:19 +01:00
domrichardson	f9c3fc5379	updates	2026-06-16 09:57:03 +01:00
domrichardson	aaf154168e	updates	2026-06-15 16:20:26 +01:00
domrichardson	c9868b2108	first commit	2026-06-15 13:58:45 +01:00