0
Fork 0
mirror of https://github.com/oblien/openship.git synced 2026-11-18 06:55:56 +00:00
Commit graph

11 commits

Author SHA1 Message Date
Rudi
3d8ff5bbc7
feat(servers): configure build-cache budgets and fix migration progress (#1645)
* fix(build): scale the managed build-cache budget with the disk

The managed project-cache budget was min(5 GiB, 10% of the Docker
filesystem). A project whose BuildKit cache outgrew 5 GiB was evicted by
the post-build prune after every build, so every deploy started cold.

- buildCacheKeepBytes is now 20% of the Docker filesystem, so the budget
  follows the disk in both directions: disks under 50 GiB also move from
  10% to 20%. This also applies to managed Cloud workers, which share
  the collector.
- Below the 20% free-space GC target the idle budget shrinks to what
  still fits above it (never below the old min(5 GiB, 10%)), so idle
  caches give space back before rollback artifacts and running apps.
  BuildKit's own 20% minFreeSpace still bounds a running worker.
- pruneManagedBuildCaches defaults to that budget instead of 5 GiB.
- The daily sweep marks its call as automaticRetention, so managed caches
  use the same budget; keepStorageBytes still bounds native Docker cache.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* feat(servers): configurable build-cache budget per server

Adds an optional managed build-cache budget for remote deployment
servers, edited from a Build cache card on the server Overview tab and
through the existing server update API, CLI and MCP tool. Empty keeps the
automatic share of the Docker filesystem.

- servers.build_cache_budget_bytes (migration 0224), bounded 1 GiB to
  64 TiB in the database and the API contract.
- Only remote deployment servers expose and accept it: the local row
  builds through the host daemon's native cache and migration sources
  never build, so updates there are refused; managed Cloud servers keep
  rejecting every field except name. Changing it requires server admin,
  since a large budget lets caches hold most of the disk.
- SSH Docker runtimes read the value through a new buildCacheBudgetBytes
  connection option on every collection, so a change applies to the next
  build without reconnecting. It sets the post-build prune budget,
  BuildKit's maxUsedSpace and the daily sweep's managed budget, capped at
  the filesystem minus the admission reserve and still reduced under
  storage pressure; a failed read falls back to automatic.
- Updates are audited like gpuOverride and do not drop retained SSH
  sessions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: regenerate the MCP and CLI references for the build-cache budget

The server update tool description and the `server configure` help now
mention the build-cache budget, so the generated references changed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(migration): frame streamed rsync progress updates

* fix(migration): preserve exact progress with rsync byte units

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
2026-11-07 20:23:30 +02:00
Hydra de lerne
9ab270c95c
feat(updates): add scoped host patches and observable advisory scans (#1566)
* feat(updates): allow workspace admins to pause runtime advisory checks

* fix(updates): repair upgrade fixture and reuse shared policy guards

* feat(updates): add scoped host patches and observable advisory scans

* fix(updates): report handled host maintenance failures

* fix(updates): load host advisory operations on demand

* refactor(updates): share server patch run lifecycle and logs

* test(cli): align compose sync with namespace isolation

* test(mail): exercise support delivery over verified TLS
2026-11-03 19:37:18 +02:00
Hydra
7753ed94cd Merge remote-tracking branch 'refs/remotes/origin/swarm-combined-main-20261022' into feat/swarm-combined-20261022
# Conflicts:
#	apps/api/src/modules/system/server-management.routes.ts
#	packages/adapters/src/index.ts
#	packages/db/drizzle/meta/_journal.json
2026-10-22 17:12:15 +03:00
Hydra
bc796d0d4f fix(manage): enforce tenant isolation across hosted server operations 2026-10-21 20:52:31 +03:00
Hydra
0d63b536c7 fix(swarm): preserve config delivery and verify lifecycle boundaries 2026-10-21 03:33:20 +03:00
Hydra
b752089aee feat(swarm): inspect existing clusters and protect scheduler-owned workloads 2026-10-21 01:34:28 +03:00
Hydra
f68fc50579 fix(billing): continue pricing selections directly to checkout 2026-10-14 03:19:58 +03:00
Hydra
87774503b9 feat(servers): add managed outbound controls and prioritize access 2026-10-11 16:06:12 +03:00
Hydra
8c0d381787 feat(cli): cover Cloud and remote platform operations through the SDK 2026-10-07 17:33:10 +03:00
Hydra
ecbaad3994 update icon system, enhance backup 2026-09-25 13:53:12 +03:00
Hydra
e75eedbcc0 fix docs 2026-09-14 03:47:37 +03:00