Skip to content

Let owners update their self-hosted Compose server when idle - #102

Open
heyyykk3 wants to merge 1 commit into
DuskBotAI:mainfrom
heyyykk3:feat/self-hosted-server-updates
Open

heyyykk3 wants to merge 1 commit into
DuskBotAI:mainfrom
heyyykk3:feat/self-hosted-server-updates

Conversation

@heyyykk3

@heyyykk3 heyyykk3 commented Nov 19, 2026 •

Copy link
Copy Markdown

What and why

On v0.2.22, the Docker server answers /api/updates/check with available: false before consulting a release source. An owner looking at that workspace in the Mac app sees “up to date” even when a newer server exists.

This adds stable release detection for official images. Owners of single-owner Compose workspaces can use Update now or opt in to automatic updates when idle. Both the browser and the linked desktop workspace send the action to the selected server. Existing 0.2.22 installs need one manual upgrade to a release containing this code.

The optional Linux host helper uses Python's standard library and the operator's existing Compose project. The only new mount is a read-only directory containing its control socket. The helper redeems a one-use owner request against its own container, checks the image and effective project configuration, pulls the matching stable release, and reserves the idle server immediately before replacement. It verifies the running image, reported server version, health and Caddy's network namespace. The owner gets a failure reason and can retry. Pins, locally built images and other deployment layouts retain their operator-managed upgrade path.

Closes #101.

How it was checked

  • A disposable Linux Docker daemon ran the production helper, server bundle, official Compose file and Caddy against a temporary registry. An authenticated owner updated fixture version 1.0.0 to 1.0.1. With automatic updates explicitly enabled in the fixture, a fake-engine turn kept 1.0.1 running. The turn completed successfully before 1.0.2 replaced it.
  • The same owner session reached the new version through Caddy. All three named volumes, a file in the data volume, a host environment setting and the completed conversation survived. The fixture also exercised anonymous and client-only denial, an invalid socket request, an operator pin, mismatched registry tags and a subsequent ordinary Compose upgrade to a pinned tag.
  • A disposable Mac Electron window using the production remote-workspace preload exercised the real Settings controls against fixture HTTP responses. The release checker also read the public GitHub feed and identified v0.2.22 as newer than 0.2.21.
  • Typecheck, lint, locale validation, the server build and 148 focused tests passed. I stopped the full local pnpm test run after it reported failures outside the updater coverage. I reproduced failures in the team-computer, trigger, chat-download and locale-test-selection cases on the unmodified base.
v0.2.22 remote workspace With the host updater
Old workspace reporting up to date Workspace offering Update now and the idle update switch

Created with GPT-6.2 Astra in the Codex harness.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Let owners update the official self-hosted Compose server from its workspace

1 participant