← Журнал изменений

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 выпуск
16 окт.2026v0.9.2ОсобенностиБезопасность39 обновлений

Рабочие и планировщики

  • Запускайте роли рядом с вашим веб-приложением

    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

    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.

  • Постоянно используйте владеющую учетную запись Cloud

    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.

Каталог, графические процессоры и общие базы данных

  • Добавьте документ, панель мониторинга и мультимедийные приложения.

    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.

  • Запускайте локальные приложения искусственного интеллекта

    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.

Почта, безопасность и локализация

  • Сохранение подключения к серверной части веб-почты

    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.

Обновите API, а также клиенты рабочего стола/панели мониторинга перед использованием новых настроек, операций управляемого туннеля или рецептов каталога, для которых требуется версия 0.9.2. Включенные миграции баз данных выполняются при обычном запуске API.