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

v0.8.0

Scale applications, PostgreSQL and Redis across your own servers, connect those servers through private networking, and share files between application instances. This release also adds the Node.js SDK, expands MCP automation, refreshes the dashboard and desktop experience, and brings the deployment, environment, routing, backup, mail and security fixes accumulated since 0.7.2.

1 выпуск
27 сент.2026v0.8.0ОсобенностиИсправленияБезопасность62 обновлений

Кластеры серверов и частные сети

  • Подключайте серверы разных провайдеров

    Register and verify an existing private network or prepare an Openship-managed WireGuard network across your servers. Provider network groups retain their provider and network details; managed networking also supports custom infrastructure (#899, #900).

  • Сети и вычислительные кластеры имеют отдельные обязанности.

    The Networking tab owns addresses, connectivity and network operations. The Clusters tab groups selected servers from a private network and manages the runtime used by their projects.

  • Выберите, какие серверы могут связаться друг с другом

    Edit connections in the network topology, allow traffic in both directions or one direction, or remove a connection. Openship enforces the private-access policy on supported hosts and shows the provider firewall rules to apply before setup. Cluster setup checks that its selected servers have the bidirectional connectivity it requires.

  • Проверьте сеть по топологии

    On-demand checks verify allowed paths and confirm that denied directions reject new connections. Results include TCP/UDP reachability, MTU, round-trip latency, loss and jitter; a selected pair can run a bounded throughput test. Saved results remain available for diagnosis.

  • Подготовьте, просмотрите, повторите попытку и очистите изменения в сети.

    Missing prerequisites can be installed automatically, address allocation and firewall requirements are reviewed before apply, and reconnectable progress includes per-server steps and errors. Interrupted work exposes explicit retry or rollback. Failed members can be removed from setup, and removal reverts owned network changes.

  • Подготовьте серверы к масштабированию приложений

    Self-hosted and desktop controllers install k3s under the hood, join the selected SSH servers, and verify node readiness, pod traffic, service routing and internal DNS. Saved progress supports retry after failure or interruption; runtime removal checks dependent workloads and owned infrastructure first (#912).

Масштабирование приложений

  • Запуск приложения или рабочего процесса на ваших серверах

    Select a prepared cluster, publish the application's image to a shared registry, and deploy through the normal project flow. Set 1–100 replicas; subsequent replica changes reuse the active immutable image without rebuilding. Openship Edge routes public requests to the application, and the topology shows observed instances, placement and readiness.

  • Обновление, откат и восстановление запущенных приложений

    Cluster deployments retain image history for rollback, and failed or cancelled candidate releases preserve the active release. Kubernetes replaces failed instances within the prepared cluster and routes to surviving ready instances after detecting an unavailable worker. Revision checks reject stale changes to a running project.

  • Подключайте общие файлы в экземплярах приложений.

    Project-owned shared volumes can be attached at configured paths, including read-only mounts. Instances on different servers can read and write the same files; existing node-local mounts require a separate data migration.

Базы данных и общее хранилище

  • Выберите автономный или кластерный PostgreSQL

    Managed databases have their own resources, progress, credentials and lifecycle. PostgreSQL clusters provide replicas, primary recovery, and private read/write and read-only endpoints. The database controller owns replication and failover independently of the application's replica count.

  • Запустите Redis автономно или в составе кластера

    Redis clusters distribute data across shards with replicas. Grow or reduce the shard count after reviewing the change and taking a verified recent backup. Redis Cluster requires a cluster-aware client; resizing checks real cluster health and slot ownership.

  • Резервное копирование и восстановление PostgreSQL и Redis

    Configure an eligible S3 destination for manual, hourly or daily backups. Restore a verified archive into a separate database, inspect it, then explicitly replace the application's saved connection and redeploy. Redis archives preserve values and expiry and are consistent per shard, rather than one transaction across all shards.

  • Импортируйте существующие базы данных и выполните PostgreSQL обновлений.

    Import eligible Docker PostgreSQL or Redis backups while the original application remains on Docker. PostgreSQL 17-to-18 upgrades create a separate logical copy for checking before connection replacement. Source data remains available; changes after the captured recovery point need a fresh capture before final cutover.

  • Делитесь файлами с независимыми копиями дисков

    Enable shared storage on at least two independent servers, choose two or three copies, and create project-owned volumes. Inspect attachment and copy health, grow a mounted volume, and rebuild a lost disk copy.

  • Восстановление файлов за пределами кластера

    Take manual or scheduled external backups and restore them into a new shared volume. Archives remain discoverable after deleting the original volume or removing empty shared storage; archive deletion is an explicit separate action.

  • Сохранять данные при удалении базы данных

    Removal can retain its data for later recovery or explicitly delete it. Application, volume, storage and runtime cleanup enforce dependencies and ownership, so an unfinished cleanup or retained database cannot silently lose the infrastructure it still needs.

SDK, CLI и MCP

  • Node.js SDK вместе с CLI

    Этот openship пакет теперь предоставляет OpenshipClient через openship/client для удаленных установок и createShip через openship/native для встроенного движка без отдельного сервера API. Оба используют общие операции платформы, проверку и авторизацию. Собственные экземпляры имеют явные жизненные циклы запуска и закрытия и проверенные области рабочей области; ESM и CommonJS поддерживаются в Node.js 22 и более поздних версиях (#887).

  • MCP охватывает большую часть эксплуатационного жизненного цикла

    Networking, cluster setup, replica scaling, managed databases, shared files, backup/restore, migration, routing and diagnostics have documented tools and ordered workflow prompts. Discovery respects workspace permissions and instance mode; required arguments and DELETE bodies survive dispatch, and path arguments cannot redirect a call to another route. Generated API, CLI and MCP references describe the available operations and explicitly excluded HTTP-only routes (#953).

  • Рабочие процессы CLI используют общий SDK.

    Native mode and remote clients share deployment and source handling, and Jobs now has commands for its existing management and execution flows. Re-login preserves custom context endpoints, folder uploads require explicit opt-in, project display names can be changed safely, and failed component installation returns a failure to the caller.

Развертывания и сборки

  • Запустите команды выпуска перед активацией

    Configure releaseCommands в настройках сборки, openship.json или API/SDK проекта. Команды выполняются по порядку после сборки с использованием среды потенциального выпуска, с потоковыми журналами и десятиминутным бюджетом на команду. Сбой, тайм-аут или отмена останавливают активацию. Поддерживаются развертывания для одного приложения Docker и Bare; неподдерживаемые типы развертывания отклоняют настроенные команды. При откате они пропускаются, а откат кода приложения не отменяет изменения базы данных (#592).

  • Завершение и затраченное время сохраняются при повторных попытках и обновлении.

    Workers retry a failed database completion acknowledgement without repeating deployment work. Cancellation records its outcome and duration atomically; late worker results cannot replace them. Both build views use the same persisted timing, including queued starts, rejected retries and terminal events (#940).

  • Удержание отката имеет предсказуемый предел

    Project → Advanced → Rollback history defaults to five past deployments, with active and pinned deployments kept in addition. Cleanup runs after deployment and retention changes, retries failed removals, and preserves artifacts still referenced by another retained release. Older history remains browsable with pagination and accurate snapshot labels.

  • Более надежные исходные сборки

    Recursive Git submodules are fetched for build checkouts; Ruby builds respect declared versions and preserve Rails storage; PHP builds include EXIF and package assets needed by frontend builds. JavaScript PORT назначения обнаруживаются, создание недействительного пустого монорепозитория отклоняется, а сбои службы DNS во время сборки получают действенное объяснение.

  • Ошибки развертывания достигают пользовательского интерфейса

    Rejected submissions show the API's specific validation or configuration error. Build streams reconnect without replaying output, and successful deployments can show live service logs. Preview variable sets cannot be deployed onto a production project's runtime.

Окружающая среда и композиция

  • Сохраненные служебные переменные остаются видимыми

    The Environment tab reads effective values from Openship, including Compose values, shared project variables and explicit service overrides, with their sources. It remains usable when the server is offline. Saves update only edited rows, preserve untouched secrets, reject conflicting edits and remove an override by restoring inheritance where available (#926).

  • Обновления создания применяются без рутинного утверждения.

    Repository changes merge automatically while explicit operator overrides remain. Saved environment values survive omitted source keys, unresolved expressions and legacy review resolution. Interpolation uses current configured values instead of stale scan results; legacy pending reviews reconcile on redeploy (#893, #916).

  • Целенаправленно восстанавливайте и применяйте изменения среды.

    Older or migrated services can recover missing variables from their running container for review and saving, without overwriting saved values. Apply compares against the running service and recreates supported Docker services from their existing image, retaining ports, networks, mounts and resource limits. Failed startup restores the previous container; unavailable comparisons remain unknown, and unsupported runtimes direct the operator to redeploy.

  • Загрузка среды и защита секрета

    Download .env exports the listed values, including saved secrets, using quoting that round-trips through Upload .env. Inline service environment, build arguments and their saved deployment/Compose snapshots are now encrypted at rest; API presentation masks protected values and preserves them on round trips (#844).

Миграция и переносимость

  • Составная миграция включает в себя передачу домена.

    Discovery reports existing proxies and matches Traefik routes through private container addresses as well as published ports. The wizard saves service environment and selected routes, prepares Edge during migration, and requests confirmation before taking over an existing proxy. Selected sites attach to their migrated services, existing certificates are reused, and unresolved routing prevents automatic source container removal (#905, #908).

  • Повторное использование сервиса в разных проектах

    Shared service connections retain the service's owner, data and connection settings instead of duplicating it. Existing Docker private links require separate migration when moving an application to a cluster.

  • Экспортируйте конфигурацию, среду и учетные данные проекта.

    Project settings download a portable plaintext file without a passphrase. The export identifies its server and Cloud dependencies; import previews the contents and requires explicit target mappings. Runtime data stays on its original server, and Cloud projects require the same Openship Cloud account. Imported credentials are encrypted with the destination instance's key. Configuration transfer does not copy runtime volumes or perform a whole-instance server cutover.

Домены и сертификаты

  • HTTPS с подстановочными знаками и автоматической проверкой DNS или ручной проверкой TXT.

    Project and service domains such as *.example.com теперь откройте встроенную настройку сертификата. Поставщики подключенных DNS автоматизируют проверку; Ручные заказы TXT сохраняют свой ход при повторном подключении и перезапуске контроллера. API, SDK и MCP используют одни и те же операции запуска, статуса, проверки и отмены. Существующие сертификаты выдерживают неудачные попытки, а HTTPS сообщается о готовности только после того, как его маршрут становится активным. Сертификаты, выданные вручную, включают инструкции по продлению на всех девяти языках панели управления (#954).

  • Управление несколькими доменами с подстановочными знаками

    Configure wildcard domains in Settings and choose the domain to use during project setup (#819).

  • Повторные попытки маршрутизации согласовывают сохраненное и активное состояние

    Retry routing checks Edge, reapplies project routes and synchronizes domains, with inline progress logs and refreshed results. Live ownership checks recover stale hostname/host-port reservations left by deleted or recreated projects. Repairs preserve complete routes and canonical endpoints when aliases are removed (#915, #922, #925).

  • Ожидающие состояния объясняют, что произойдет дальше

    Domain details distinguish verification in progress, scheduled retry and failure, show the reason and next retry time, and offer a manual retry. Durable backoff prevents overlapping background sweeps from repeatedly retrying the same domain. An SSH observation failure no longer clears a working certificate or becomes a claim that HTTPS is absent (#911, #922).

  • Импортированные сертификаты и маршруты контейнеров восстанавливаются правильно.

    Certificate lookup follows managed lineages and avoids collisions after import; recovery excludes ACME challenge ports from application upstreams. Static sites inside containers route through their owning service, and Edge serves an Openship error page for unavailable upstreams (#879, #913).

Резервные копии и восстановление

  • Сделайте резервную копию прямо сейчас из проекта, службы или панели тома.

    Service shortcuts reuse an applicable policy and run only the selected service. Project policies skip stateless services and admit their eligible runs together. Progress shows saved phases, elapsed time and transferred bytes, reconnects across workers, and updates recent history even after the progress view is dismissed.

  • Дополнительные инкрементные резервные копии

    Policies can reuse verified unchanged blocks, with a complete block index for each restore point. Retention preserves blocks still referenced by another snapshot, and storage totals count shared objects once. Full backups remain the default. Captures still scan the whole source and transfer through the Openship backup worker.

  • Хранение и места назначения остаются неизменными

    Pruning runs after successful capture and through the scheduled sweep, preserving protected copies and backups used by active restores. Existing runs retain their original destination when a policy changes, and failed cleanup remains retryable without invalidating a successful backup. SFTP failures close streams and clean partial uploads instead of leaving the worker stuck (#817).

  • Восстановление проверяет перед заменой данных

    Preparation and confirmed apply share source/target checks, integrity verification and exclusive access to the project or mail server. Runtime/stop failures abort before destructive writes; partial-write failures are reported and do not automatically restart a service on incomplete volume data. Redis/Valkey restore validates persistence settings, and PostgreSQL restore uses a transaction for each supported artifact. Release tests now exercise backup, incremental reuse, retention and restore with real Docker volumes and databases (#892, #946).

GitHub и доступ

  • Подключения к облаку GitHub завершаются на панели управления.

    Installation completion refreshes repository access and the connection state instead of leaving the page loading after GitHub has finished. Device sign-in keeps its code and instructions visible until completion; transient and rate-limit failures no longer discard durable credentials (#920, #951).

  • Выбор репозитория остается синхронизированным

    Branches load on demand while keeping selection and keyboard focus, and changing the branch rescans deployment configuration. Partially successful push-webhook dispatches retry failed targets without redeploying targets that already completed (#847, #870).

  • Вход в систему и приглашения соответствуют настроенному процессу.

    Clients can discover enabled login providers, and signed-out invitees can reach account creation and complete acceptance without the dashboard's prior navigation race.

Панель управления и рабочий стол

  • Общие значки и более согласованные макеты

    Dashboard and desktop use a theme-aware icon catalog with bundled local assets. Service headers, tabs, environment controls, volume forms, source settings and log controls have consistent spacing and typography; mobile navigation and crowded rows are improved (#942, #946).

  • Топология остается внутри проекта

    The graph has an optional expanded view, improved loading placeholders and compact service nodes. Clicking a node opens its details directly; long runtime identifiers truncate with copy actions rather than widening the panel.

  • На страницах развертывания действия и журналы ставятся на первое место.

    Open site and Open project remain prominent, multiple exposed domains can be selected, and preparation, service status and single-app steps share clearer progress indicators. Logs have bounded layout, search and copy controls; history filters survive returning from a deployment.

  • На страницах резервного копирования отображаются сохраненные данные и реальное состояние работы.

    Global and destination views share paginated history, restore actions and usage information. Successful retained copies, active attempts and physical storage totals are distinguished; history remains available after policy changes.

  • Запуск рабочего стола соответствует теме приложения.

    A redesigned loading screen uses shared colors, clearer progress and service startup states (#952).

Мониторинг и надежность во время выполнения

  • Мониторинг восстанавливается после прерывания соединения

    Desktop connectivity loss is distinguished from a confirmed remote runtime failure, with recheck and reconnection handling. Overlapping status requests no longer stop polling or replace newer results, and issue feeds remain available when a host adapter cannot start. Services show a checking state while runtime status is unknown (#927, #949, #951).

  • В представлениях трафика используются одни и те же временные ряды.

    Overview and monitoring render timestamped request buckets with clear time ranges, area/column views and loading skeletons. Analytics failures stay within the affected view instead of appearing as empty traffic or replacing fresh data with stale responses.

  • Долго работающие ресурсы ограничиваются и освобождаются.

    Container log retention is bounded for newly created managed containers, session caches preserve active work at capacity, and closed log, terminal and IMAP streams release their subscriptions. Busy builds retain their SSH transport; abandoned terminal handshakes release their slots and resumed shells remain bound to the authorized target (#950, #951).

  • Администрация сервера сообщает о сбоях, требующих принятия мер.

    MacOS hosts expose system statistics, server responses match shared diagnostics contracts, and deletion refuses hosts with active deployments. SSH group refresh preserves active sessions after Docker installation.

Облако и API

  • Выставление счетов в облаке соответствует выбранной организации.

    Plans, checkout, credit top-ups and renewal management use Oblien namespace entitlements. Purchased limits survive catalog changes, deployment/recovery checks enforce available capacity, and checkout completion verifies payment delivery rather than trusting the return URL. Billing portals remain scoped to the organization (#910).

  • Автономные API ограничивают флуды без аутентификации.

    A separate per-IP guard runs before authentication without consuming the route's own limit. Cloud mode or explicit OPENSHIP_TRUST_EDGE=true делегирует этот внешний потолок восходящему прокси-серверу, сохраняя при этом ограничения для каждого маршрута (# 123).

Почта

  • Проверьте и обновите сертификаты, которые фактически используют почтовые клиенты.

    Mail settings show expiry and the certificates served by SMTP and IMAP, with actions to check and renew them. Successful renewal reloads Postfix and Dovecot and verifies the served certificates. Automatic renewal uses the shared scheduler; expiry, renewal failures and stale served certificates appear in Health and Monitoring. Scheduled renewal requires the Openship controller to remain running.

  • Веб-почта обновляется без дублирующих подписок

    Inbox updates use a single owned SSE/IMAP IDLE connection with cleanup on disconnect. Replies fill recipients and subject correctly, Trash uses IMAP deletion, and mobile composer, accessibility and browser-cache failures are corrected (#897, #904, #921, #950).

  • Блокировка удаленного контента также распространяется на CSS.

    Disabling remote images prevents CSS imports and URL-based fetches from leaking a read receipt (#220).

  • Настройка, доставка и оповещения почты стали более надежными

    Setup distinguishes an unverified public SMTP probe from a stopped server; database port selection handles conflicts; mounted certificates and Amavis state recover on restart. Relay TLS and SES MAIL FROM checks are corrected, delivery health evaluates the full queue, and captured messages remain until notification delivery is durably queued. Job and backup notifications include their relevant target, outcome and log details (#834, #865, #867, #945, #951).

Выпуск чеков

  • Продолжить неопубликованный выпуск с обновленным кодом

    Reuse successful whole checks only when their source and workflow inputs match, and rerun failed or affected checks. Artifact reuse verifies the original run and immutable artifact identity; concurrent tag changes and earlier publishing attempts prevent unsafe continuation.

  • Реальные этапы принятия приложений, баз данных и общего хранилища

    Release checks exercise MCP dispatch, image publication, deployment, public routing, scaling, updates, rollback, worker recovery and project cleanup. Separate database tests verify real queries, replica/shard changes, backups, restores, imports and upgraded copies. Shared-storage tests use independent Linux VMs for SSH installation, cross-server writes, volume growth, disk-copy rebuilding and external backup recovery. These heavier journeys run in the release gate or on demand.

Примечания к обновлению

  • Масштабирование области действия в этом выпуске

    Cluster management is available from self-hosted and desktop controllers. Application scaling supports single apps and workers with project-owned shared files. Compose application scaling, CPU/traffic-driven autoscaling, automatic server provisioning and live cluster membership changes are not included.

  • Храните базу данных и ключ шифрования вместе

    This release includes database migrations and converts legacy plaintext service configuration when the engine starts. Back up the database and retain the instance encryption key (BETTER_AUTH_SECRET для установки API) перед обновлением. Для перехода на версию, предшествующую этой защите, требуется соответствующая резервная копия базы данных. Используйте передачу данных с включенными секретами при перемещении конфигурации между экземплярами с разными ключами.