Skip to content

v0.1.5b: trainer cards link straight to profile pages

Choose a tag to compare

@Hailey-Ross Hailey-Ross released this 04 Jul 04:30
fab44bc

What's New

Trainer Directory: cards link straight to profiles

  • Clicking a trainer card now opens that trainer's full profile page instead of an in-page popup
  • Profile pages show everything the popup did and more: identity and badges, trainer code, awards, and the shiny collection
  • The View profile link on each card is unchanged; the whole card is now a shortcut to the same place

Smaller improvements

  • The popup and its supporting code were removed (about 400 lines of markup, script, and styles), so the directory page ships less to the browser
  • Migrate tool: v0.1.5b added to the baseline version map (no new sections; it maps to section 42 like v0.1.5a)

Upgrading from v0.1.5a

No database changes. Redeploy the binary and templates as usual; the migrate tool will report nothing pending:

go run ./cmd/migrate -status   # expect: 42 applied, 0 pending

Upgrading from v0.1.4a or earlier

This release includes everything from v0.1.5a (self-service password reset, email confirmation at signup, and the transactional email schema), so older installs have one database section to apply (42: transactional email). With a tracked install:

go run ./cmd/migrate -status   # see applied vs pending
go run ./cmd/migrate           # applies what is pending, through section 42

First time using the migrate tool on an untracked install:

go run ./cmd/migrate -from v0.1.4a   # baseline at YOUR installed version, then apply the rest

The tool knows every release from v0.1.1a through v0.1.5b and lists them if you pass an unknown version. Or apply the pending migrate.sql sections manually, in order. Then redeploy the binary and templates as usual.

Optional environment variables from v0.1.5a: RESEND_API_KEY and MAIL_FROM enable transactional email (see the Configuration wiki page). Leave them unset and password reset and signup confirmation simply skip sending. BASE_URL controls the origin used in emailed links and defaults to the production site. For the full rundown of what you pick up along the way, read the v0.1.5a release notes.

Fresh install

Run schema.sql only. It already reflects every migration through section 42 and seeds the migration history. Do not also run migrate.sql.

Documentation