← 変更履歴

v0.9.2

This patch adds worker and scheduler execution, personal appearance customization, and managed Cloudflare Tunnel setup for self-hosted servers. Cloud spaces, reusable build caches, more catalog apps and safer storage cleanup improve everyday operations. These notes cover all merged changes since 0.9.1.

1 リリース
10月16日2026v0.9.2特長セキュリティ39 件の更新情報

ワーカーとスケジューラ

  • Web アプリの横でロールを実行する

    Declare workers and schedulers in openship.json またはプロジェクト API。単一アプリ Docker のデプロイでは、共有環境、ボリュームと接続されたネットワーク、独自のコマンドとシャットダウン設定を使用して、アプリ イメージから別のコンテナーが開始され、公開ポートはありません。ロールは、一時停止、再開、再起動、ロールバック、プロジェクトの削除に続きます。

  • シングルトンを安全に引き渡す

    Scheduler renames, command changes, name swaps and conversions into workers stop and retain outgoing singletons before starting potentially conflicting replacements. Failed deployments restore them only after those replacements are confirmed removed. Failed retirement of an old role is surfaced in the deployment warning with its container identity.

  • 検証済みの起動を要求する

    Every replica needs exactly one stable result for its container ID before optional exec health checks run. Missing inspections, duplicate results and processes that already exited successfully fail startup. Both project-defined and image-inherited PORT 値がロールから削除されます。

  • ロール構成を明示的にする

    Move and copy refuse active, unfinished or preserved-cancelled role workloads even after saved roles are cleared. Preset-only when そして unless 宣言されたロール内のキーは、実行を制御するために黙って現れるのではなく、警告を生成します。フレームワークの役割の自動選択とサーバー間の役割の移行は含まれません。

  • フレームワークのシャットダウンのデフォルトを改善する

    Rails presets have measured stop settings, and Laravel's scheduler preset uses SIGTERM with a 10-second grace period while queue and Horizon workers retain 90 seconds. Customize these bounds for long-running tasks; they do not guarantee task completion or exactly-once scheduling. Laravel web-role cache warming is available as an opt-in setting.

外観とダッシュボード

  • 自分の外観をカスタマイズする

    Settings → General → Customize previews color tokens and typography live, with explicit Save, Discard and Reset. Import themes from JSON, a file or an HTTPS URL; export themes and libraries, including supported WOFF2 fonts. Preferences belong to the signed-in user and stay isolated across accounts and instances. API, SDK, CLI and MCP operations use the same theme format.

  • 運用ツールをまとめて保管する

    Project monitoring and logs share one navigation entry with their own views. Backups moves under Infrastructure. Project sidebars show assigned domains, migration retries retain destination choices, and migrated service deployments use the correct icons.

  • 誤った停止アラートを削減する

    The health watcher confirms repeated bounded Docker probe failures before announcing a server outage. Late probe replies cannot falsely announce recovery. Self-hosted administrators can clear resolved monitoring history with confirmation while retaining open incidents.

  • ナビゲーションと端末の信頼性を向上させる

    GitHub discovery no longer blocks dashboard pages, selection controls use consistent states, and leaving a server terminal during WebGL loading cancels setup and disposes the terminal. Instance connection and move actions have clearer setup and recovery guidance.

Cloudflare トンネルとドメイン

  • OpenShip からのセルフホスト型 Ingress を管理します

    Server → Security can connect or create a remotely managed named Cloudflare Tunnel using saved credentials, configure proxied DNS and optionally apply an existing reusable Access policy. Install a pinned connector on a supported Linux server or use its existing connector. Managed Openship Cloud routing retains its existing path.

  • 回復可能なセットアップを使用してドメインを登録する

    Explicitly enable automatic tunnel enrollment for new custom domains or connect existing domains individually. Setup records Access, tunnel and DNS progress, supports retry after interrupted requests, and removes only owned resources. External edits remain visible for review instead of being overwritten. Exact hostnames and www コンパニオンはサポートされています。ワイルドカード自動登録は機能しません。

  • プライマリおよび www の動作を選択する

    The deployment wizard defaults a newly included companion hostname to a 301 redirect to the entered primary. Choose bare primary, www primary or Serve both on Cloud and self-hosted destinations. Redirect rows show their target instead of duplicate runtime inputs.

  • ドメイン運用の一貫性を保つ

    Service aliases on the same port are preserved, domains added through the CLI receive routing, and Cloud routing retries recover missing Pages through the owning Cloud connection.

  • コンテナ化されたエッジで信頼できるプロキシを尊重する

    Operator-declared proxy IPs reach the edge without rebuilding its image. Invalid addresses and CIDR prefixes are discarded. Failed configuration updates restore the previous shared trust include, and an incomplete rollback cannot activate a partial configuration.

クラウドスペース、請求、接続

  • 管理対象容量をクラウドスペースとして見る

    A shared picker, Overview and Activity views show projects, purchased capacity and measured usage, with clear retry states for unavailable readings. Existing allocations and subscriptions keep their identity; connected self-hosted server tools remain available.

  • 所有するクラウド アカウントを一貫して使用する

    Connected Desktop and self-hosted installations create Cloud projects through Cloud's API. Server, project and deployment operations enforce their organization and provider namespace. Cloud consent shows the actual account and organization and lets you switch either before explicitly authorizing the connection.

  • プランの選択を繰り返さずに購入を続行

    Pricing links carry the chosen plan into the signed-in app's checkout flow. Pending unpaid payments can be cancelled when supported by the provider so another plan can be selected; retries retain the original payment identity. Server cancellation is easier to find and repeated requests cannot create duplicate operations.

  • 既存のスペースでアクションを構成する

    Cloud's Add runner flow opens the capability form directly with the space picker. Local Actions lists remain available when Cloud discovery fails, and official runner containers support non-root SSH supervisors. Temporary runner profiles retain their separate funding flow.

  • インスタンスのソースとのハンドオフを維持する

    Control-plane provisioning on a linked managed destination stays owned by the source controller until the move transfers the instance, including resumed API-only and dashboard installations.

ビルドのパフォーマンスとリソース制御

  • 未構成のリソースには上限を設けないでください

    Omitted build and service CPU/RAM limits no longer become sampled capacity caps or catalog sizing recommendations. Containers share the selected server's capacity unless limits are explicitly configured. Cloud plans and VM capacity still apply. Existing saved limits are preserved; select Full capacity to remove an older unwanted limit.

  • クラウドへの同時送信を許可する

    Different projects can submit builds while a sibling build is active. Unspecified resource dimensions remain shared; explicit limits, saved plan concurrency and exclusive maintenance protection remain enforced.

  • 制限されたプロジェクトのビルド キャッシュを再利用する

    Compatible builds retain project-owned BuildKit state and supported package/compiler caches while temporary workers are removed. Idle cache collection uses retention targets and storage-pressure checks, preserving active workers, release images and application data.

  • オプションでウォームな新しいクラウドスペース

    Operators can select a provider software disk with public build-image layers for new spaces. Matching images are pinned against their current upstream digest; unavailable or outdated packs fall back to registry resolution. Existing spaces are not reattached by an API redeploy.

  • 画像の準備が何を行っているかを表示する

    Registry pulls stream progress, preparation heartbeats and elapsed time into deployment logs. Build cleanup waits for tracked Docker commands to acknowledge completion, and static export publication normalizes public file permissions.

カタログ、GPU、共有データベース

  • ドキュメント、ダッシュボード、メディア アプリを追加する

    Install Paperless-ngx, Wiki.js, Homepage, Immich and Jellyfin using pinned published images, persistent storage and protected initial setup. Homepage does not require a Docker socket.

  • 自己ホスト型 AI アプリを実行する

    Ollama offers CPU or one NVIDIA GPU, and Open WebUI connects to an existing backend with protected chat access. These templates use connected self-hosted destinations, not managed Cloud capacity. vLLM remains a disabled preview pending hardware verification.

  • NVIDIA GPU サービスを導入する

    Compose import, SDK/CLI sync and adoption share validated GPU selection and Docker device requests. Server detection and picker hints help choose a compatible destination. Unsupported or conflicting requests fail before image acquisition or service replacement.

  • 不要な WordPress と Odoo ビルドをスキップする

    New catalog installs pull the official images and mount setup helpers through the normal deployment engine. Existing installations retain their saved recipes; reviewed catalog repair can update the application service while preserving database siblings, credentials and data.

  • ネイティブデータベースを明示的に共有する

    Use in a project can connect ready native PostgreSQL or Redis databases to authorized projects in the same cluster. Saved grants and private network rules are checked together; ownership, backups and database management stay with the source project.

保存、削除、移行の安全性

  • 新しいクラウド アプリ データを分離する

    New logical volume names use immutable project IDs so reinstalling a deleted slug cannot adopt another project's data. Owned legacy mounts and explicitly imported volume identities remain intact.

  • 失敗した削除を明確に復元する

    Failed first installs offer the existing explicit data-removal option, including owned volumes with no container. Data retention stays the default. Cleanup failures remain retryable operations instead of making a partly deleted project appear Live again.

  • 他のプロジェクトに属するリソースを保存する

    Teardown can retain stale Cloud route and network references whose foreign ownership is confirmed. Unreadable or ambiguous ownership still blocks cleanup, and owned networks are removed by immutable identity rather than a potentially reused name.

  • 一時的なホストとポートの衝突を回避する

    Docker allocation checks the target kernel's ephemeral range for both saved preferred ports and fresh candidates. Unsafe legacy allocations move to a safe port during deployment; if no safe candidate exists, allocation fails before reserving a replacement.

メール、セキュリティ、ローカリゼーション

  • Webメールのバックエンド接続を維持する

    Webmail deployed on its mail server saves the host-gateway mapping through normal service settings and deployment snapshots while retaining the certificate hostname for TLS. Sign-in connection attempts have bounded timeouts rather than hanging indefinitely.

  • クラウドから既存のメールボックスを接続する

    The Emails screen installs the standard webmail client for existing IMAP/SMTP servers. It does not provision or administer a self-hosted mail server in Cloud; managed email remains Coming soon.

  • コンテナ化されたメール操作を修復する

    Boot restores maildir ownership, backups and restores use the actual host-mounted mail path, and fail2ban uses valid nftables syntax and explicit private PostgreSQL sidecar credentials. Database and unban failures no longer report success.

  • 受信トレイと閲覧ウィンドウのサイズを変更する

    Drag the divider or use its keyboard controls. Desktop widths are remembered separately from the mobile layout.

  • ダッシュボードのクリックジャッキングを防止する

    Dashboard pages, authentication routes and redirects deny framing through CSP and X-Frame-Options. Customer application routing and headers are unchanged.

  • 翻訳されたガイダンスとドキュメントを拡張する

    Supported dashboard locales include preferences, transfer, jobs, issues, pricing, diagnostics and audit descriptions. The website adds a blog and broader feature discovery, alongside updated catalog, runtime-role, Cloud, API, SDK, CLI and MCP documentation.

0.9.2 を必要とする新しい設定、管理されたトンネル操作、カタログ レシピを使用する前に、API とデスクトップ/ダッシュボード クライアントを更新してください。含まれているデータベースの移行は、通常の API 起動を通じて実行されます。