24. Okt.2026v0.9.4FunktionenKorrekturenSicherheitBreaking80 AktualisierungenLink kopieren
Projekte, Repositories und Umgebung
Wählen Sie aus, welche Monorepo-Apps bereitgestellt werden sollen
New imports ask for an explicit app selection instead of enabling every detected package or port. Add more apps, browse or enter repository folders, and retain saved selections, manually added roots, custom commands and private access when rescanning or reopening a project.
Halten Sie große Domainlisten überschaubar
The wizard groups routes by their owning app, shows a total and the first three rows, and offers View all. Apps using the same port keep separate domain ownership; changing deployment mode preserves the selected app's routes and privacy settings.
Erstellen Sie zusätzliche Dienste aus dem Repository
Services and Topology share a From repository form with folder, build-context and Dockerfile selection. Save the service, then deploy it through the normal pipeline. Manual paths and retry remain available when browsing fails. Catalog selection gains compact source tabs, search and category filtering while retaining generated credentials.
Compose-Topologie während der Erkennung beibehalten
A root Dockerfile alongside a Compose file retains the declared services and volumes even when framework detection also matches. Development-only Compose files beside ordinary framework projects remain opt-in; explicitly selected configuration retains precedence.
Überspringen Sie Pushvorgänge, die nichts mit dem Arbeitsbereich zu tun haben
Single-app subfolder projects consider transitive workspace dependencies, shared build inputs and lockfiles before automatic deployment. The update banner uses the same decision. Configure
autoDeployPaths.includeundexcludefür explizite Regeln; Die unsichere Analyse behält die Bereitstellung bei, anstatt Änderungen stillschweigend zu überspringen.Lesen Sie die angeforderte Quellrevision konsequent durch
Retries and explicit-commit deployments read Compose files and
openship.jsonStandardwerte aus diesem Commit, anstatt einen älteren Checkout mit der neuesten Konfiguration des Zweigs zu mischen.Verwenden Sie eine effektive Umgebungsansicht
The Compose wizard and service editor resolve defaults and interpolation consistently while preserving the original templates and masked secrets. Save persists intentional service edits; existing projects also offer Cancel without writing changes. Revealed values and late lookup responses no longer restore an old value after saving.
Klären Sie das Speichern und Anwenden von Umgebungsänderungen
Save and Apply & restart describe their separate effects. Runtime-only values appear in a compact disclosure, unchanged image defaults no longer produce recovery warnings, and Apply can resolve an owned live legacy service without a populated per-service deployment record. Missing containers lead to the existing deployment action.
Vollständige GitHub Verbindungen und private Klone
Hosted App setup, installation selection and attempt polling use the owning Cloud connection consistently. Self-hosted App creation sends a valid manifest redirect URL. Authorized same-owner private submodules receive scoped, short-lived credentials without persisting tokens in clone URLs or Git configuration.
Zeigen Sie, wo Builds tatsächlich ausgeführt werden
Remote Docker deployments no longer offer an unsupported local-image build or label a remote build as local. Genuine local bare builds and independent clone-location choices remain available.
Bereitstellungen, Speicherung und Wiederherstellung
Rufen Sie verwaltete Worker-Images aus Paketinstallationen ab
Bundled workspace files no longer make a release installation look like a development checkout. Automatic source builds require Git checkout metadata; explicit administrator build contexts still work for source archives. Remote builds use the published protected worker matching the release.
Sichern Sie den eigenständigen App-Speicher
Project backup policies now capture a single app's persistent volumes even when it has no service rows. Manual, scheduled and pre-deploy runs share the existing backup and restore flow, including integrity verification, confirmation and retention. App restore points remain distinct from deleted-service history (#1444).
Verwenden Sie Freigabebefehle und -rollen mit angeschlossener Infrastruktur
Supported self-hosted/Desktop Docker projects can keep one primary source app on the normal release-command, worker and scheduler pipeline while preparing attached private image services first. Infrastructure health gates app activation; retries, cancellation and rollback preserve confirmed databases and volumes. General Compose, multiple source apps, Cloud and cluster targets retain their existing role/release-command restrictions.
Erklären Sie nicht unterstützte Rollenkonfigurationen
Refusals describe which saved release command or role must change instead of recommending the Docker runtime already in use. Eligible older projects without a persisted runtime mode can configure roles through the same runtime resolver as deployment.
Überprüfen Sie vor dem Erstellen die erforderlichen Compose-Variablen
Validate the effective enabled service cohort before image builds, registry pulls or cutover. Errors list missing keys by service without exposing values; frozen rollback settings and explicit service scopes retain their existing precedence.
Wiederholen Sie einen abgeschlossenen Docker Build
Retry deployment can reuse a retained, ownership-verified image after activation fails. It preserves the source revision and destination, with no rebuild or replacement pull. Missing artifacts fail clearly; unsupported bare/static and source-bind attempts do not offer an image-only retry.
Laufzeitbilder gezielt aktualisieren
The wizard exposes runtime versions, build images and production images. On-demand checks compare available image digests, and Refresh images & redeploy uses the normal readiness and rollback pipeline. Configured version tags, digest pins and deployment scope stay intact; unavailable comparisons remain unknown and pins never advance automatically.
Bewahren Sie den Amtsinhaber durch qualifizierte Compose-Ersetzungen
Supported self-hosted Docker deployments can prepare an overlapping candidate when saved limits, measured headroom, port provenance and storage compatibility permit it. The old service remains until routing and the successful release are committed. Other targets keep normal replacement order; concurrent writable storage needs an explicit opt-in for the exact mount.
Beenden Sie die unterbrochene Routing-Wiederherstellung, bevor Sie einen erneuten Versuch zulassen
A timed-out Compose recovery requests cancellation and waits for its in-flight route pass to finish before releasing deployment ownership. Uncertain recovery retains the containers needed for recovery instead of allowing a late route write to overwrite a newer deployment.
Behalten Sie die im Bild deklarierten Daten bei erneuten Bereitstellungen bei
Self-hosted and Desktop-managed Docker replacements reuse stable project-owned volumes for image
VOLUMEErklärungen. Legacy-Speicher wird aus dem exakt verifizierten Ausgangscontainer wiederhergestellt; Fehlender oder widersprüchlicher Besitz stoppt die Bereitstellung, anstatt eine nicht verwandte verwaiste Datei anzuhängen oder mit leeren Daten zu beginnen. Explizite Bereitstellungen haben Vorrang und beibehaltene eigene Volumes werden in der Löschvorschau angezeigt.Erfordern Arbeitspersistenz für Bare-Bereitstellungen
Provision writable build, shared-data, process metadata and log directories through the deployment login. Persistence failures stop activation instead of silently leaving data inside a replaceable release directory. Hosts needing one-time permission setup receive actionable guidance.
Starten Sie einen Dienst mit leerem Speicher, ohne seine alten Daten zu löschen
Writable named volumes offer Start with empty storage, with service-name confirmation and a preview of the new and retained volume names. The existing service deployment applies the change; failed admission can retry the same saved volume selection. Other mounts, backups and the previous volume remain available for recovery.
Passen Sie die Artefaktaufbewahrung an die Festplattenkapazität an
Automatic retention can reclaim eligible older Docker release artifacts under measured storage pressure while protecting active releases, pins, shared references and ongoing work. Reclamation requires a verified rebuild or immutable-image recovery path. Managed idle-cache budgets scale with filesystem size; application containers and volumes are excluded from pressure cleanup.
Melden Sie nützliche Wiederherstellungsfehler
When a Docker restore helper exits without delivering its diagnostic output, collect a bounded tail of its logs. Stalled or unavailable log reads cannot hide the original failure or indefinitely delay cancellation and helper cleanup. Restore ordering and the separate attach-input issue are unchanged.
Wenden Sie Updates der Compose-Steuerungsebene zuverlässig an
Explicit updates recreate API, dashboard and edge services even when an earlier image prefetch already changed the environment. Updates wait for application readiness and report failures; PostgreSQL and Redis are not targets of forced recreation.
Machen Sie die Austauschsteuerung pro Dienst verfügbar
Opt into
resources.swapDisabledfür unterstützte Docker Dienste mit einem positiven Speicherlimit und überprüfter Swap-Buchhaltung. Durch die gemeinsame Validierung bleibt die erforderliche Obergrenze für Konfigurationsänderungen erhalten. Dadurch wird der ausgewählte Dienst geändert, ohne den hostweiten Swap zu ändern oder neue Build-Limits festzulegen.Halten Sie die Bereitstellungszeiten genau
Build measurements survive terminal outcome writes, service timings include image preparation, and measurements freeze before cleanup. Unknown durations remain unknown, skipped builds display
0s, und unberührte Dienste erwerben keine erfundenen Maße.
Cluster, Skalierung und Topologie
Bereitstellung für einen vorhandenen Docker Schwarm
Desktop and self-hosted controllers can inspect an existing Linux manager, connect its cluster, and deploy new application or Compose workloads through the shared deployment, routing, scaling and rollback flow. Nodes pull immutable image digests and use release-scoped secrets. Existing Swarm tasks and routing-mesh ports stay protected from standalone adoption and edge takeover. Moving a previously deployed project requires an explicit migration.
Überprüfen Sie die Skalierung und Datenbankreplikation
Topology Scale reviews application changes before applying them. Self-hosted Kubernetes can manage PostgreSQL readers and authenticated Redis/Sentinel replication through the existing operators, with verified backups and explicit writer/reader connection changes. Reader removal checks dependent consumers; unsafe Redis reductions use a verified smaller copy that preserves the original until the connection switch is approved. Swarm application scaling remains supported; synchronized database replication requires Kubernetes and is separate from copying a database.
Siehe Datenbankmitglieder in der Übersicht
Primary and replica cards show their observed roles, health, servers and replication links. Larger graphs can switch to a compact view; Redis Sentinel voters remain distinct from data replicas. Missing observations do not invent a primary or a running member.
Machen Sie die Einrichtung und Wiederherstellung von K3s klarer
Require cgroup v2 before installation, prefer This Server for the initial gateway/control roles, and correct private kubelet connectivity. Retries can migrate an unchanged Openship-owned legacy configuration and finish its required restart; edited or unverified configurations stop with bounded, credential-redacted diagnostics.
Domänen, Eingang und Zertifikate
Schützen Sie selbst gehostete Routen und native Vorschauen mit einem Passwort
Configure a shared password at the OpenResty edge. Authenticated requests verify a signed browser cookie locally, without an API, database or Redis lookup per request. Public routes keep their existing path. Password changes and revocation invalidate sessions; protected responses disable caching.
Beenden Sie Service-Routing und HTTPS gemeinsam
Project and service domain saves share the existing routing preparation and certificate checks. First-route setup uses an inline progress viewer, retains explicit edge/DNS-01 consent, and refreshes canonical status after success or partial failure. A ready proxy no longer masks a failed or disconnected HTTPS check.
Veröffentlichen Sie reine Weiterleitungsdomänen ohne Zielport
Compose
www/apex redirects can reach the edge even when the domain has no upstream service port.Sorgen Sie für routenfreie Workloads unabhängig vom Edge
Private deployments without hostname routes skip unnecessary edge takeover, challenge and vhost preparation. Fixed-port services retain their explicit bindings; automatic allocations still require verified inventory and durable port claims.
Öffnen Sie pgAdmin ohne eine benutzerdefinierte Domäne
PostgreSQL + pgAdmin supports an explicit Port only option while PostgreSQL stays internal. New catalog services also generate required PostgreSQL, MySQL, MariaDB, MongoDB and Typesense credentials instead of leaving their bootstrap secrets empty.
Halten Sie Katalogbilder verfügbar
Convex uses its new official registry namespace with the existing version pin. The retired Mindwire Console/runtime template is hidden and disabled for new installs; existing project data stays unchanged.
Verwenden Sie gültige übergeordnete Wildcard-Zertifikate wieder
Immediate subdomains can inherit a validated parent wildcard certificate when an exact certificate is absent. Exact certificates retain precedence; read failures preserve the working route rather than initiating replacement issuance or copying private keys.
Ersetzen Sie manuelle Zertifikate, ohne den Erneuerungsstatus zu unterbrechen
Remove only the selected hostname's obsolete Certbot renewal record after validation. Failed installation restores the prior certificate, key or archive links and renewal configuration before any reload; unrelated lineages remain intact.
Verbessern Sie die Routing-Wiederherstellung und -Diagnose
Control-plane setup can reclaim its own quarantined dashboard port without taking another workload's claim. ACME 502/504 errors describe challenge forwarding and the temporary listener; safe Cloud routing errors retain their actionable cause instead of blaming a healthy server connection.
Behalten Sie die Tunnelverwaltung im Routenmenü bei
Cloudflare Tunnel settings move into the existing context menu, retaining per-domain Access settings, retry and readiness behavior without a persistent management row on every card.
Cloud, Abrechnung, Überwachung und Aktionen
Verwalten Sie die kundeneigene Infrastruktur aus der Cloud
Openship Manage Basic costs $5/month per organization with email support; Priority costs $20/month with priority support. Both include two connected servers, plus $3/month per extra server. Paid Cloud includes the Basic allowance once per organization; Priority retains its support fee. Expiration ends management access after the paid period while applications and data remain on the customer's hosts. Self-hosted control planes remain free.
Wählen Sie zwischen monatlicher oder jährlicher Cloud-Abrechnung
Hobby, Starter, Pro and Scale cost $12, $24, $47 and $119 per month, or $120, $240, $468 and $1,188 billed annually. The purchase view defaults to Yearly when supported by the provider, shows the monthly equivalent and full annual charge, and retains an explicit Monthly switch. Custom resources use the selected interval through quote, checkout and plan changes. Existing subscriptions retain their saved prices and allowances.
Aktualisieren Sie die Cloud-Kapazität der Einstiegsklasse
New Hobby purchases include 1 vCPU, 4 GB RAM, 50 GB storage and email support. New Scale offers allow 50 projects. These catalog changes do not rewrite existing paid contracts.
Vereinfachen Sie die Planauswahl und die Zahlungsrückerstattung
Cloud plans, Prepaid PAYG and Manage your server share the purchase view. Manage plans are also available directly when connecting a server. Pending purchases appear under Payments & invoices with a count, and Manage checkout keeps the server allowance and total beside the selected support plan.
Halten Sie die Managementabrechnung und den Zugriff koordiniert
Durable checkout intent and receipt validation protect purchase retries. Paid Cloud organizations receive their included management allowance once, and allowance changes coordinate with server connections. Increasing recurring charges after Cloud coverage ends requires explicit consent.
Beheben Sie ausstehende Checkout-Konflikte
Explain when a purchase must be completed or cancelled, and open the existing payment recovery dialog. Checkout limits, pending resource changes, verification failures and cancellation in progress receive specific guidance instead of a generic retry message.
Cloud-Nutzungsströme erneut verbinden
Interrupted read-only subscriptions recover from retryable disconnects with bounded backoff. Authentication failures, malformed data and stalled subscriptions still fail clearly; cancellation releases readers, requests and timers.
Stellen Sie verwaiste Cloud-Terminals präzise wieder her
Refresh expiring namespace credentials for dispatch and teardown, then recover only the marked commands belonging to the interrupted operation. Ownership is cleared only after confirmed process exit; live controllers and another installation's claims remain protected.
Verwenden Sie bereichsbezogene Anbieteranmeldeinformationen wieder und behalten Sie die Drosselungsanleitung bei
Concurrent Cloud lookups share short-lived namespace tokens after ownership checks. Rejected token generations are invalidated without evicting newer credentials or replaying mutations. HTTP 429/503 and bounded Retry-After guidance survive the transport.
Erklären Sie ressourcenbezogene Bereitstellungsfehler
Supported OOM, heap-limit and storage evidence produces a saved diagnosis and Review capacity action for the affected Cloud space. The explanation survives reloads and compacted logs. Long builds receive optional advice rather than an invented capacity failure; upgrades and retries remain explicit.
Reflektieren Sie Laufzeitvorfälle im Projektstatus
Known incidents on the active self-hosted workload show Action Required and link to Monitoring & Logs. Status clears after observed recovery; intentional stops, retired workloads and monitoring opt-outs do not create stale attention.
Berechnen Sie Antwortdurchschnitte aus Anfragen
Overview and CLI traffic metrics divide total request duration by total request count, with consistent millisecond conversion for Cloud and self-hosted data. Uneven traffic and live/archive refreshes no longer inflate the reported average. Edge collection is unchanged.
Behalten Sie aktive Actions-Runner bei vorübergehenden API-Ausfällen bei
Retry transient provider, GitHub and App-token renewal failures without cancelling the worker, releasing its capacity or silently falling back to broader user credentials. Persist supervisor completion before external cleanup and retain verified infrastructure errors when GitHub synchronization finishes.
Führen Sie den Aktionsverlauf zuverlässig zusammen
Local timestamps and Cloud date strings sort together without crashing the Actions page. Failed Cloud augmentation preserves the local run list. Service connection/unlink messages also reflect the existing automatic deployment attempt instead of asking users to trigger it twice.
Behalten Sie während Kontoänderungen einen aktiven persönlichen Arbeitsbereich bei
Deleting or leaving the selected team workspace restores the stored session owner's personal workspace instead of failing while clearing the active organization.
Sicherheit und Anmeldeinformationen
Patchen Sie die DOM-Testumgebung
Dashboard and webmail tests use Happy DOM 21.0.4, which fixes the module import alias code-execution vulnerability (GHSA-834v-8h66-3h79).
Passen Sie Laufzeitsicherheitshinweise an bereitgestellte Arbeitslasten an
Verify a public, signed advisory feed and match affected image digests or observed runtime versions. New runtime rules, deployment changes and Check again refresh bounded container observations; ordinary polling reuses one current observation per project. Findings appear in the existing global critical/update banner with a shared affected-app review; no project visit is needed. The banner reads cached, workspace-authorized evidence without probing containers. Missing evidence stays unknown. Initial notices cover Node.js/Bun Brotli fixes and PHP's October security guidance, including a separate manual configuration warning that an image update alone cannot clear.
Wenden Sie überprüfte Patches über die Bereitstellungspipeline an
Refresh images & redeploy can pull a replacement behind the same tag, or rebuild the deployed Git revision with refreshed base images. Automatic refresh is off by default and requires explicit consent, a signed affected/fixed digest pair, an eligible image service and unchanged configuration. It pins the approved replacement, uses the normal refresh and environment-resolution flow, preserves persistent volumes, and verifies the deployed result. Late environment changes stop an automatic update for review. Concurrent requests admit one automatic attempt; rollback clears the one-time approval. Explicit digest pins remain fixed.
Übermitteln Sie Sicherheitshinweise über bestehende Benachrichtigungskanäle
Verified, enabled channels receive matching alerts by default, with a per-channel opt-out and durable delivery deduplication. Feed checks share authentication-aware polling, conditional requests and backoff with release updates: five minutes when authenticated, one hour without authentication. Advisory metadata cannot supply executable commands.
Anheften von gepatchten Laufzeiten und Build-Tools
Use Node 22.23.4 and Bun 1.4.4 across the affected control-plane, website, webmail and worker image stages, with verified image digests. Desktop moves to supported Electron 44.9.2; Actions distributions use Go 1.26.9 and updated Git, archive, SSH/HTTP and telemetry dependencies.
Behalten Sie Laufzeitregressionen bei Release-Prüfungen bei
Exercise the upstream Brotli decoder rejection case, streaming input, private-CA HTTPS, hostname verification and authenticated asynchronous WebSockets. TLS SNI is sent only for DNS names, and package-manager bootstrapping works when
nodeist ein Alias für Bun.Behalten Sie die Autorität über Mieter- und Terminalgrenzen hinweg
Service, server and proxied Cloud terminals retain the caller's credential restrictions and recheck expiry, revocation and current administrative access. SaaS-managed customer hosts use verified public destinations, SSH host-key pins and encrypted uploaded credentials; operator identities and private certificate-provider settings remain outside tenant-controlled host configuration.
Umfang der Backup-Verbindungen zum Zeitpunkt der Nutzung
Cloud S3/SFTP destinations pass the shared public-network checks before connecting to the validated address. Server SSH identity and existing host-key pins remain enforced for SFTP; self-hosted private backup storage stays supported.
Gewähren Sie engere Token-Funktionen
Personal access tokens and MCP clients can receive project-scoped domain read/write/delete and deployment read/trigger permissions. Minting checks the creator's authority, and cancellation, rollback and deployment deletion retain their administrative requirement.
Schützen Sie Remote-Builds Docker vor Metadatenzielen
Rootful Linux SSH and Cloud builds use the project-owned BuildKit worker's IPv4/IPv6 metadata and credential-endpoint policy, including after restart. Missing required executor or policy support fails before repository commands; local Engine API, bare and Kubernetes builds remain outside this policy's scope.
Überprüfen Sie die Worker-Veröffentlichung, bevor Sie abhängige Pakete freigeben
Publish and anonymously verify the protected worker for both supported Linux architectures before dependent image and bundled-release publication. Release receipts must match the tag and source commit; missing or private images stop publication.
Halten Sie deaktivierte Vorschaudienste isoliert
Disabled service copies retain their disabled state while host bind mounts and external host/container namespace references are removed. Named/anonymous volumes and sibling service references stay usable; production configuration is unchanged.
Separate Kontingente für Webhook-Endpunkte hinter gemeinsam genutzten Adressen
Unrelated hooks no longer exhaust one another's source-IP bucket. Endpoint quotas share the existing limiter with a separate aggregate IP ceiling; authentication, signatures and credential redaction remain enforced.
Desktop, Webmail, Website und Dokumentation
Erstellen Sie Windows Installationsprogramme mit gepatchten Laufzeiten
Stage SSH and Docker dependencies from a package manifest so version ranges do not pass through Windows command shims. The packaged dependency load check remains required.
Sichtbaren Offline-Desktop-Start wiederherstellen
Embed the shared generated theme palette in the native loading page so its text and artwork remain visible before the dashboard loads.
Reparieren Sie ältere verwaltete Webmail-Hostzuordnungen
Backfill the missing host-gateway alias for the explicitly linked webmail service on its own self-hosted mail server. The repair preserves credentials and volumes and takes effect through the next normal deployment.
Vorschau von Office-Anhängen mit begrenzter Darstellung
XLSX, DOCX and CSV files gain readable, sandboxed previews with limits on parsing and rendered content. Unsupported, encrypted, corrupt or truncated content retains a download option. Active HTML/SVG/XML and unknown attachment types download instead of executing in the signed-in webmail origin.
Aktualisieren Sie E-Mail- und Editor-Abhängigkeiten konsistent
Align the patched editor dependency graph across direct and nested imports, update Nodemailer and Mailparser, and preserve reviewed runtime overrides in Docker and tarball packages. Existing SMTP modes and credential repair remain supported.
Sorgen Sie dafür, dass die sozialen Vorschauen auf öffentlichen Seiten erhalten bleiben
Pricing, marketing, catalog, feature, blog, changelog and mail-guide pages inherit the shared Open Graph and Twitter images while retaining explicit page images and metadata. The release checks validate the rendered image tags and their image responses.
GitHub Sterne in der Seitennavigation anzeigen
Desktop and mobile navigation display the cached repository star count, with an accessible exact count and a fallback when GitHub is unavailable.
Verbessern Sie die operative Führung
Document Docker socket permissions and reconnecting after group changes, update the shared API/SDK/CLI/MCP references, and explain the supported cluster, recovery and runtime-image workflows.
Upgrade-Hinweise
Rebuild or recreate the affected control-plane and webmail deployments to apply their runtime updates. Explicit project runtime versions and image digest pins are preserved
Updating Openship alone does not update every deployed app.
- Geschützte Root-SSH-Builds Docker erfordern Buildx und Root oder kennwortloses Sudo für die Trusted-Worker-Richtlinie und Cache-Dateisystemvorgänge. Gewöhnliche explizite CPU-/RAM-Grenzwerte und nicht konfigurierte Ressourcenfreigabe behalten ihr bestehendes Verhalten bei.
- Die Unterstützung für vorhandenen Schwarm gilt für Desktop-/selbstgehostete Controller mit Stop-First-Cutover und persistenten Einzelinstanzdiensten auf dem verbundenen Manager. Es übernimmt keine beliebigen vorhandenen Stacks und fügt kein gehostetes Cloud-Clustering hinzu. Für die verwaltete PostgreSQL/Redis Replikation sind selbstgehostete Kubernetes Operatoren erforderlich.