19 Releases 150 Tags

RSS Feed

• v0.10.9-beta.1 053adb311d

  Compare

  fix(applications): keep distinct compose projects apart; refuse multi-project backup jobs

  LastSkywalker released this 2026-09-06 10:51:32 +03:00 | 66 commits to main since this release

  A "Big Bear" card on a CasaOS host grouped Dozzle, Home Assistant and NocoDB
  into one application because every store app is named big-bear-. The
  prefix grouping exists for Dokploy, whose swarm services carry no compose
  project label and have nothing else to group them by. Here each member DID
  carry its own label and its own compose file — the signal that they are
  physically separate stacks — and merging them broke the backup/update path
  in two ways:

  • two projects both name their main service "app", so keying services by
    name alone made Home Assistant disappear behind Dozzle in the picker;
  • worse, the executor drives compose -p <one project> and matches
    services by name across the card's compose files, so updating Dozzle
    would have rewritten Home Assistant's compose to the Dozzle image, while
    compose stop addressed a project that does not exist (a hot snapshot
    of a running Postgres) and up -d collided on container names.

  Grouping now leaves a prefix group unmerged when its members span two or
  more file-backed compose projects. Dokploy grouping is unchanged: its
  services have no compose file, so the count stays at zero. Reproduced with
  the exact labels from the affected host.

  The plan additionally refuses any card that still spans several compose
  projects, whatever the grouping does — that guard sits directly in front
  of the executor, which must never be handed a multi-project job.

  Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com

  Downloads

  • Source Code (ZIP)
  • Source Code (TAR.GZ)