Files
proof-of-work/start9/0.4/startos/versions/v1.0.0.1.ts
T
Keysat d9c4e6c4a0 Multi-user: self-serve sign-up gated by admin-toggleable flag
Schema
- User.isAdmin: Boolean default false (Prisma)
- New InstanceSettings singleton (id=1) holding signupsOpen flag

Boot-time compat ALTERs (docker_entrypoint.sh)
- Adds User.isAdmin column to legacy snapshots; auto-promotes the oldest
  user to admin if no admin exists yet, so workout-log -> proof-of-work
  cutover preserves admin functionality with no manual SQL.
- Creates InstanceSettings table + singleton row (signupsOpen=0) for any
  snapshot that doesn't have it.

App: sign-up flow
- /auth/signup page: server component that reads InstanceSettings
  upfront. If sign-ups are closed it shows a closed-instance message and
  a back-to-sign-in link rather than a dead form. If open it renders
  SignupForm (client) which calls signupAction (server).
- signupAction: re-checks the flag (defense in depth), validates email
  format / 8-char password / matching confirm, blocks duplicate-email
  enumeration with a generic error, creates the user with isAdmin=false,
  seeds default UserPreferences, ensures the curated exercise library
  for the new user (lib/library.ts upserts every entry), then issues a
  session cookie.
- Login page now links to /auth/signup; old "Demo: admin@example.com /
  password" footer (which was wrong anyway) removed.

App: admin in-app toggle
- Settings page renders new AdminInstanceSettings component for admins
  only. Optimistic toggle posts to /api/admin/signups; error rollback
  on failure.
- /api/admin/signups: GET returns current flag (any authed user, so the
  UI knows whether to show the sign-up CTA later); POST flips it
  (admin only).

StartOS package action
- toggle-signups: same setter as the in-app toggle, accessible from the
  StartOS UI without an admin login. Single boolean input. Asserts the
  read-back value matches what was written before reporting success.
- changeAdminCredentials now keys the UPDATE on
  `WHERE isAdmin = 1 ORDER BY createdAt ASC LIMIT 1` (was: just
  ORDER BY createdAt) — correct under multi-user.

Release notes / docs
- v1.0.0:1 release notes expanded to call out multi-user as part of
  the cutover release (no separate version needed since this is the
  first proof-of-work release shipping to anyone).
- Root README: short Multi-user section explaining both toggle paths
  and that new users get the curated library automatically.
- README dev setup adds `npx prisma generate` step (required after
  schema changes for local dev).
2026-05-08 20:59:45 -05:00

35 lines
1.8 KiB
TypeScript

import { IMPOSSIBLE, VersionInfo } from '@start9labs/start-sdk'
/**
* v1.0.0:1 — initial Proof of Work release.
*
* Upstream version: 1.0.0
* Wrapper rev: 1
*
* This is a one-shot "seeded cutover" release for users migrating from the
* old `workout-log` StartOS package. The Docker image bakes in a snapshot of
* the maintainer's live /data volume under /app/seed/data; the entrypoint
* copies that snapshot into the new StartOS-managed /data volume only on a
* truly-fresh first boot (both /data/app.db missing AND /data/.seeded
* absent). Every subsequent boot leaves /data untouched.
*
* Because StartOS treats `proof-of-work` as a brand new service (different
* package id from `workout-log`), the old install stays running until the
* operator confirms the cutover and stops it manually. There is no
* downgrade path; `down` is IMPOSSIBLE.
*
* The post-cutover cleanup release (v1.0.0:2) will strip the baked seed and
* the seed-copy branch from docker_entrypoint.sh.
*/
export const v_1_0_0_1 = VersionInfo.of({
version: '1.0.0:1',
releaseNotes: {
en_US:
'Initial Proof of Work release. Replaces the legacy `workout-log` package with: (1) multi-user support — anyone with the URL can sign up when admin enables it, via Settings or the new "Set new signups" StartOS action; (2) a curated exercise library shared across all users — additive on every upgrade, so new exercises shipped by the maintainer reach existing installs without overwriting users\' own custom entries; (3) one-time seeded cutover from /data on the legacy `workout-log` host so every workout, exercise, and preference comes across; (4) the `change-admin-credentials` StartOS action targeting the primary admin (User.isAdmin = 1).',
},
migrations: {
up: async () => {},
down: IMPOSSIBLE,
},
})