Switch the CI templates to the /build HTTP endpoints

README.md

@@ -9,8 +9,8 @@ projects, in the same spirit as [tic80-tools](../tic80-tools).
   `ci-binaries`, `ci-upload`, `ci-update`).
 - `example-woodpecker.yaml` — Woodpecker pipeline: version → export
   (`.love` package + love.js web build) → binaries (fused desktop
-  builds) → upload (scp to the droparea) → update (calls the
-  teletypegames `/update` endpoint with `platform=love`).
+  builds) → upload (HTTP POST to `/build/upload`) → update (calls the
+  teletypegames `/build/publish` endpoint with `platform=love`).
 - `example-tasks.json` — VS Code `.vscode/tasks.json` with the common
   dev tasks: **Run Löve** (`love .`, default build task,
   `Cmd+Shift+B`), **Build & Run Löve**, **Build .love package** and
@@ -21,13 +21,13 @@ projects, in the same spirit as [tic80-tools](../tic80-tools).
 1. Copy `example-makefile.make` to `Makefile` and set `PROJECT`
    (the package is built as `dist/$(PROJECT).love`).
 2. Copy `example-woodpecker.yaml` to `.woodpecker.yaml` and add the
-   `droparea_ssh_password` / `update_secret_key` secrets in Woodpecker.
+   `update_secret_key` secret in Woodpecker.
 3. Copy `example-tasks.json` to `.vscode/tasks.json`.
 
 The pipeline uploads `$(PROJECT)-$(VERSION).love.zip`,
 `$(PROJECT)-$(VERSION).html.zip`, the versioned `metadata.json` and
 the fused binary zips (`-win-x64.zip`, `-mac-universal.zip`,
-`-linux-x64.zip`) to the droparea, then triggers `/update` twice: once
+`-linux-x64.zip`) via `/build/upload`, then triggers `/build/publish` twice: once
 with `platform=love` (desktop package) and once with
 `platform=love-web` (web build). The API's `BinaryAttachment` concern
 picks up the `<name>-<version>-<slug>.zip` files automatically and