Commit Graph
6 Commits
Author SHA1 Message Date
aj 244f946912 ci(server): take the publication policy from master, not the tag
The publish job checks out the tag and ran that tree's release helper for
preflight and readback, so an older tag (v0.7.0 requires a private
package) could never publish under the current public policy. Copy
master's helper before checking out the tag and run preflight/readback
from it; the tag's tree is still what gets built, tested and smoked. The
helper is stdlib-only and its local identity stamp is unchanged since
v0.7.0, so the two copies agree on it.
2026-11-17 18:48:42 -05:00
aj 6f7d8049a7 ci(server): publish the server image as a public package
The repository is public, so a private image only made every deployment
host log in to ghcr.io. Publication now requires the existing package to
be public and linked to ajisaacs/OpenNest (private or wrong association
stops before upload and is rechecked after it), and the clean-runner
verification pulls the returned digest without logging in, proving
anonymous pulls work. Docs describe the one-time package setup and drop
the deployment-host login; the server itself stays LAN-only.
2026-11-17 18:45:47 -05:00
ajandClaude Opus 5.5 54ad7ee84d feat(server): nest Auto Nest jobs on the server's worker
Large nests tie up the workstation that runs them. In Database mode, Auto Nest
can now queue the job on the nest server, where a worker container solves one
job at a time under its own CPU and memory limits. The job has no time limit,
so a throttled worker finds the same nest a fast one does, only later.

- Server: /api/nest-jobs queue (schema v15). The worker holds a job on a
  heartbeat lease. When the lease lapses, the job goes back to the queue,
  or fails after three attempts. Only one job runs at a time. Packages and
  results are opaque to the HTTP server, which stays off Engine and IO.
- Worker: OpenNest.Server.Worker in the same image (OPENNEST_ROLE=worker),
  reaching the server over HTTP only. It records each engine answer with
  RecordingNestingEngine and gives its job back on shutdown.
- Desktop: "Nest on the server" in the Auto Nest dialog, for built-in
  engines only. The client replays the recorded answers with
  RemoteNestSubmission, so validation, the review and Keep run locally
  against the client's own drawings, exactly as after a local run. A
  drawing edited after sending refuses the result. If the server cannot
  take the job, the user may nest locally instead.
- compose.server.yaml adds the throttled worker service. The Dockerfile,
  .dockerignore, CI paths and the deploy script now include the worker's
  projects.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-02 13:18:09 -05:00
aj 19be5a5ece ci(server-image): publish to GHCR only by manual dispatch from master
Publishing a GitHub Release, stable or pre-release, now only validates the
server image. A desktop release and a server image release are separate
owner decisions, so a stable desktop release cannot publish an image that
has not been accepted yet.
2026-10-27 10:18:44 -04:00
aj a73a85ebc0 ci(server): skip image publication for GitHub prereleases 2026-10-08 19:17:15 -04:00
aj 1ec79ae594 ci(server): validate and publish versioned GHCR images 2026-10-02 18:53:00 -04:00