Skip to content

v0.2.0

Choose a tag to compare

@Clumsyvortex123 Clumsyvortex123 released this 04 Nov 06:54
· 4 commits to main since this release

What's new

Self-update from GitHub releases

  • Publish a GitHub release and every open board offers it: the page blurs and shows "vX is available" with the release notes, Later or Update now.
  • Update now has the server pull that release and redeploy itself. Each planner keeps its own planner.config.json, .env files and data, and is backed up first. A failed build rolls back to the previous version.
  • While it deploys, boards show Updating…. When it's live, every board offers Reload now.
  • New API: GET /api/release, POST /api/release/update (see /api/docs).
  • The deploy itself is done by a small host updater (devops/updater/), installed once per server. Without it, boards still notice a newly deployed build and offer a reload.

Developer footer

  • A small footer with a line that changes by day of the week, linking to the author's GitHub. It can be turned off per browser at the bottom of Settings.

Deployment

  • Several planners can share one server: each checkout runs its own compose.plan.yml (COMPOSE_PROJECT_NAME, PLAN_PORT), and one compose.edge.yml nginx maps each hostname to its port.
  • planner.config.json is no longer tracked. Copy planner.config.example.json to start.

Installing: this release has to be deployed by hand once, with the updater installed (see devops/updater/README.md). Later releases install themselves from the board.