← Journal des modifications

v0.8.1

Openship Cloud now runs projects on managed servers with their own monthly plans. Share a server across applications, add another when you need it, and manage your Cloud resources alongside local projects from desktop or self-hosted Openship. This release also adds passkeys, authenticator 2FA and a private support inbox, expands CLI automation, and improves billing, migration and deployment recovery.

1 version
6 oct.2026v0.8.1CaractéristiquesCorrectifsSécurité50 mises à jour

Serveurs Cloud gérés

  • Un serveur, plusieurs projets

    Each managed server has its own subscription and shared CPU, RAM and disk. Builds, applications, Compose stacks and catalog services use the existing Docker and Bare deployment engines. Creating a project no longer allocates a separate VM or reserves another disk (#1036).

  • Choisissez Docker ou Exécution directe

    Use Docker for containers and Compose, or run compatible source applications as supervised host processes with Direct. The shared destination picker can select an existing server or start a purchase for another. New eligible source apps default to Direct below 2 GiB RAM; saved projects and explicit runtime choices are preserved (#1064).

  • Utilisez la capacité que vous avez achetée

    A service can use the server's full available CPU and RAM, or use a custom container limit. Fractional CPU settings, including Micro, reach Docker correctly. Source builds use available server headroom and optional build caps; image-only installs do not start a source builder. Applications, builds and the operating system still share the host.

  • Inspecter l’utilisation séparément de la capacité

    Server monitoring distinguishes the purchased disk size from measured usage. Project containers and volumes have a disk breakdown, with shared images, build cache and system data shown separately. Missing readings stay unknown, and undeployed drafts no longer inflate running-service counts (#1011).

  • Gérez le serveur lorsque vous en avez besoin

    Reuse server diagnostics, terminals, listening-port checks and resource views. Networking controls outbound internet access; the Activity tab holds provisioning and resize logs. Scheduled command jobs can target shared or separately subscribed managed servers.

  • Récupérer les opérations sans perdre les projets voisins

    Provisioning, resize and interrupted deployment work retain progress for retry. Resizing restores previously running services while leaving intentionally stopped ones stopped. Project deletion removes its own resources and preserves the shared server; server deletion checks remaining projects and subscription state.

Comptes cloud sur ordinateur et auto-hébergés OpenShip

  • Vos ressources Cloud existantes apparaissent lorsque vous vous connectez

    Cloud projects, apps and managed servers join the local inventory. A server already linked to the installation appears once. Cloud-owned settings, deployment history and operations stay in Cloud rather than becoming local project copies (#1074).

  • Achetez et utilisez des serveurs gérés à partir du même tableau de bord

    Cloud subscriptions and provisioning remain in Cloud. Local projects can select an authorized managed server through the same destination picker as SSH servers, using an execution link for deployment, logs, terminals, jobs and backups.

  • Les changements de compte effacent l'état du compte précédent

    Inventories, project details, deployment history and billing responses follow the selected Cloud account and organization. Connections are revalidated for live operations; locally scoped automation credentials do not inherit the owner's Cloud account.

Facturation et forfaits

  • Les serveurs mensuels incluent la totalité de leur période payante

    New monthly plans cover purchased CPU, RAM and storage without a second compute-credit allowance or a monthly build-time cap. New offers have no project or running-service count limit; workloads share the server's physical capacity. Optional managed proxy transfer and storage retained after coverage ends remain separate charges.

  • Plans révisés et ressources personnalisées

    Hobby is $5/month for 1 vCPU, 4 GiB RAM and 25 GiB disk; Starter is $20 for 2 vCPU, 8 GiB and 32 GiB; Pro is $39 for 4 vCPU, 16 GiB and 128 GiB; Scale is $99 for 8 vCPU, 32 GiB and 256 GiB. Custom lets you choose CPU, RAM and disk and review a quote before checkout.

  • La facturation suit le serveur sélectionné

    Switch servers without losing the page, inspect each subscription independently, or use Obtenir le serveur pour un nouvel achat. Les nouveaux clients voient les forfaits plutôt que les écrans d'utilisation vides. Les comparaisons de mises à niveau plus petites conservent des cartes compactes et un résumé distinct du plan actuel ; les modes de paiement et les factures partagent le portail Stripe du serveur.

  • Examiner les modifications du plan avant de les appliquer

    Show the provider's prorated amount, effective date and affected projects. Capacity upgrades apply after confirmed payment; resource reductions and billing-mode changes wait until renewal. Pending changes remain visible, and a resize requires restart consent. Disks can grow but cannot shrink in place.

  • Le paiement a un chemin de récupération visible

    Payment confirmation, paid coverage and server readiness are separate steps. Setup failures expose progress and retry without asking for another purchase; the welcome dialog appears when setup completes. Unavailable offers show a dedicated dialog with retry and a support request for availability updates (#1062).

  • Reprendre ou annuler les paiements inachevés

    Paiements en attente répertorie l'offre enregistrée de chaque serveur et ouvre sa caisse d'origine. L'annulation confirmée par le fournisseur vous permet de choisir un autre forfait ou de supprimer un serveur inutilisé et non payé. Les installations cloud et connectées partagent le flux de récupération, et le changement de compte supprime les détails de paiement et les réponses du compte précédent (#1067).

  • Aperçu des niveaux PAYG prépayés

    Compare three shared resource-pool tiers, configure server resources and select a credit package in one calculator. The estimate separates active vCPU-hours, reserved RAM and storage, with hourly costs and balance-duration scenarios. Enterprise contact is available in both purchase views. PAYG purchases remain disabled in this release (#1057).

Sécurité du compte et GitHub

  • Clés d'accès et authentificateur 2FA

    Settings → Security supports passkey registration and removal, authenticator QR setup, and single-use recovery codes. Enabled 2FA also applies after social and passkey sign-in. These controls are available on Cloud and self-hosted installations with local accounts (#984).

  • La protection du compte reste cohérente en cas de panne

    Credential changes commit together, concurrent requests cannot reuse a challenge or recovery code, and password resets do not disable 2FA. OAuth, invitation and MCP handoffs resume after verification. Security setup state clears when the account changes.

  • L'accès au référentiel GitHub est indépendant de la connexion

    One GitHub identity can authorize repositories for multiple Openship accounts without transferring login ownership. Reconnect existing installations from the shared connection flow, including direct installation links, and see completion or failure for each attempt (#992).

  • Les jetons personnels fonctionnent tout au long du flux du référentiel

    Git settings remain reachable through the alternative connection option. A verified token can supply repository and owner listings and private-source access when no GitHub App connection is available. Account avatars and Git URL entry are clearer.

Assistance et intégration

  • Une boîte de réception d'assistance Cloud privée

    Submit deployment, billing, account or general tickets, search your history, reply and resolve or reopen a conversation. The same personal ticket history is available from Cloud-connected desktop and self-hosted installations. Team membership does not expose another user's tickets (#1073).

  • Les pages d'assistance et de contact acceptent les demandes durables

    Submissions are saved before email delivery, with a receipt and notification to [email protected]. Les tentatives de livraison survivent aux redémarrages de l'API et les réponses d'assistance apparaissent dans la boîte de réception et sont envoyées par courrier électronique au client. Les soumissions réessayées réutilisent leur reçu d'origine plutôt que de créer un autre ticket (#970).

  • Des écrans de première exécution et de compte plus clairs

    Refreshed Cloud plan prompts, purchase welcome dialogs, email-verification and password-reset completion screens. The home page omits empty system-status cards for new Cloud accounts, and already subscribed users do not keep seeing the first-purchase promotion.

Applications et migration

  • Les applications ont leur propre place

    A dedicated Apps sidebar entry and list keep catalog applications separate from source projects. Compact home rows, restored empty states and clickable app illustrations make discovery less cluttered.

  • Un assistant de déploiement plus cohérent

    Share destination and server controls across Cloud and self-hosted modes, with Full/Custom power choices, filled inputs, compact Build/Start settings, readable deployment-step icons and clearer draft project details. App install forms support grouped and two-column layouts.

  • L'installation de l'application explique les choix de routage et de ressources

    Public dashboards start with domain routing and ask for confirmation before continuing without a recommended domain. Self-hosted app CPU/RAM recommendations are advisory; failed Cloud installs can be retried or cleaned up without treating an absent runtime as a teardown failure (#1009, #1016).

  • Importer Docker applications dans des serveurs cloud gérés

    Reuse the existing migration engine for images, environment, volumes, bind data and routes. Cloud can connect an external SSH server as a migration-only source. Target preparation, saved progress, verification and explicit cutover support recovery; source data is preserved and source-container retirement requires consent.

  • Examiner les importations sous forme de cartes ou de topologie

    Compact expandable service cards are the default, with a topology view, expand-all controls, repository linking and clearer Custom, Free and Internal-only routing choices.

Builds, déploiements et récupération

  • Stop annule le constructeur sélectionné

    Cancellation reaches the worker's actual Docker or Bare runtime, including remote Git and archive preparation. The UI shows Arrêter… jusqu'à ce que le nettoyage soit terminé, puis permet le redéploiement. L'annulation d'une build préserve les conteneurs déployés qui ont hérité des étiquettes de build ; la propriété ambiguë du service bloque toujours l'activation (#1059).

  • La sortie de build reste lisible

    Cloud Docker streams preserve raw bytes, partial lines, UTF-8 characters and terminal progress updates. Uploads finish correctly when stdin closes. Disk and inode exhaustion are explained separately from memory failures, and temporary BuildKit cache is reclaimed after builds (#1058, #1064).

  • Les services Compose inchangés restent opérationnels

    Folder uploads and snapshot syncs no longer mark unchanged image services dirty. Import metadata preserves concurrent configuration edits; inherited project resource changes still apply while respecting per-service overrides (#989).

  • Les sauvegardes de pré-déploiement se terminent avant l'activation

    Deployments wait for all configured pre-deploy backups and their cleanup, including when reusing a build. Failed backups offer retry, an explicit skip or stop. PostgreSQL dumps must succeed, and suspiciously small dumps are rejected against recent comparable backups before becoming restore points (#1060).

  • Les versions distantes et les versions statiques utilisent les bons chemins

    Subfolder refreshes preserve root manifests and rescan at the project root. Static output resolves relative to that root, and retained artifacts are checked on their deployment destination for rollback. Directory-only .dockerignore les négations sont honorées (#1010, #1041).

  • Les contrôles de santé et l'arrêt respectent le temps d'exécution

    Configured single-app readiness probes run through the deployment server; unreachable SSH leaves a check unverified. Docker replacement honors stop signals and grace periods, probe watchdogs are reaped, and Bare services retain the correct user privileges and artifact ownership (#1043).

  • Détection Farm.js

    Identify Farm.js applications and supply the framework's build and output defaults (#1037).

Domaines, mise en réseau et surveillance

  • Les domaines gratuits suivent le serveur géré sélectionné

    Availability and quota checks retain the destination through project creation, Compose synchronization and deployment. Route changes are validated before related settings are saved; editing an existing route at the limit does not count it as a new route (#1064).

  • Connectez Cloudflare à partir de la configuration du domaine

    Add and verify a DNS credential without leaving the DNS panel, review proposed records, then apply them. Cloudflare TXT quoting and Cloud certificate-status handling are corrected, while certificate checks verify the domain's project binding (#977).

  • HTTPS générique et récupération Edge plus fiables

    DNS challenge hooks pass Certbot validation, Compose installations detect Edge correctly, and challenge route cleanup checks ownership. Whole-project rules handle a null path prefix correctly. Projects no longer have the unrelated 20-public-endpoint schema cap (#1054, #1003, #1017, #1045).

  • Les mises à jour sources restent visibles jusqu'à la fin du déploiement

    The project deployment tab indicates available updates; unchanged image services are not refreshed unnecessarily. Updates on the local Openship instance use the appropriate advisory flow, and resource reporting accepts current Docker runtime limits (#1006, #1047).

  • Correctifs de connexion et de configuration

    Recover Cloud Docker connections after credential rotation, report missing proxy/bridge failures clearly, correct registry TLS/WebSocket dependency compatibility, and handle Docker networks without subnets during cluster setup (#970, #1068, #961).

Correctifs du SDK, de la CLI et de la plateforme

  • Plus d'administration via Ship SDK et la CLI

    Add commands for project resources, environments, storage and connections; credentials and DNS; monitoring, notifications and webhooks; workspace access and audit history. They use the shared platform operations and permission checks.

  • Ciblage des commandes et modifications de l'environnement plus sûrs

    Each CLI invocation keeps its selected endpoint, credential and organization. Directory links reject mismatched contexts. Partial service environment edits preserve other values and secret classification; full replacement is explicit. Deployment waits have deadlines and expose pending decisions, and request logs can be followed through the SDK's authorized Cloud stream.

  • Des flux de travail MCP Cloud plus clairs

    Discover authorized managed destinations and deploy desktop folders through a connected server. Explicit promotion to Cloud can resume from its saved receipt after an interrupted response or cleanup, without importing the project again (#1056).

  • Corrections du webmail et du tableau de bord

    Spam, Not spam and Archive move messages into the correct IMAP folders. Notification settings and icons recover from hydration races, Teams accepts current Microsoft webhook hosts, member-access settings avoid repeated refetches, and background project deletion preserves navigation (#981, #1004, #1008, #1035, #1024, #1066).

  • Démarrage de l'API et validation des actions groupées

    Capacity previews pass the startup permission scan, and malformed bulk container requests are rejected instead of being interpreted as an empty request (#1033, #994).

  • Analyse facultative des produits Cloud

    The hosted Cloud API can send configured PostHog events for signup, deployment and verified checkout/payment outcomes. Delivery is queued separately from those operations. Telemetry runs only on the hosted Cloud API; local operations, logs, secrets and session recordings are excluded.

Notes sur le transfert de données et la mise à niveau

  • Exportations complètes et portables

    Instance and project archives include plaintext environment values, server keys and credentials by default, without an export password. Treat the archive as sensitive or explicitly omit secrets. Imports still accept older encrypted archives and encrypt credentials with the destination's key.

  • Les importations préservent la portée et les données sélectionnées

    Instance imports default to full replacement after confirmation. Project overwrite removes destination-only records in selected categories and applies cleared credentials atomically. Project analytics retain normalized hostnames, including www; les champs d'archives non pris en charge sont rejetés avant de modifier les données.

  • Mettre à niveau le Cloud avant les clients connectés

    New inventory and support features require the matching Cloud API. Desktop-initiated cancellation fixes require an updated desktop controller. Existing per-project Cloud deployments need an explicit migration to managed servers; updating alone does not consolidate VMs or replace saved subscription terms.

  • Maintenir la stabilité de la configuration de sécurité du compte

    Self-hosted passkeys require HTTPS and a stable dashboard hostname through OPENSHIP_PUBLIC_URL (localhost est pris en charge pour le développement). Conserver et sauvegarder BETTER_AUTH_SECRET, qui protège les secrets d'authentification et les codes de récupération.