← Journal des modifications

v0.9.1

This patch adds a public app catalog, Russian dashboard support and runtime image controls. It fixes workflow saves and Cloud recovery, updates webmail live, and improves routing, build capacity and image handling during redeployments. These notes cover all changes since 0.9.0.

1 version
13 oct.2026v0.9.1CaractéristiquesCorrectifs16 mises à jour

Configuration des applications, de la langue et du flux de travail

  • Parcourir les applications avant de les installer

    The public website now has an Apps directory with search, category filters and individual pages showing features, included services and app overviews. Installation opens the existing Cloud setup flow; self-hosted users can follow the installation guide. Returning to the directory preserves search and category selections.

  • Prise en charge de la langue russe

    Select Russian during onboarding or in dashboard language settings. Dashboard translations cover workflow setup, Cloud reconnect and webmail recovery, and a Russian README is available alongside the existing localized introductions.

  • Enregistrer les workflows d'actions personnalisés

    New standalone workflows initialize their name from validated YAML, so valid starter workflows can be saved after setup. Missing names, runners, files, source validation or access settings now have inline guidance that leads back to the relevant control or editor. Repository setup also offers a direct custom-workflow option.

Récupération cloud et webmail

  • Poursuivre les installations d'applications et la sélection de forfaits après la connexion

    App and plan links retain their destination through login, registration, verification, password reset and 2FA. App installation resumes its confirmed configuration, server and existing draft after checkout; failed retries remain recoverable. Plan links select an offer for review, with an explicit action still required to purchase.

  • Reconnecter les liens de serveur Cloud enregistrés

    Disconnected links show a Cloud sign-in action, with separate guidance for account mismatches and temporary failures. Live controls wait for a verified connection, and reconnecting reuses the saved server link. Controls missing from an older Cloud API show availability guidance; refreshing retries reads without repeating a write.

  • Récupérer une application de messagerie Web existante

    When a mail registration loses its webmail link, select an accessible existing app on the same mail server and hostname and choose Reconnecter et déployer. La récupération réutilise le projet, les informations d'identification et les volumes persistants tout en préservant la propriété du domaine et les contrôles d'autorisation.

Configuration du runtime et sécurité du déploiement

  • Sélectionnez les versions d'exécution correspondantes et les images de production personnalisées

    Generated PHP builds support PHP 8.3 and 8.4 through the generic runtimeVersion réglage. Docker versions sources offrent une fonctionnalité avancée runtimeImage outrepasser. Les recettes sélectionnées dans la pile valident les capacités d'exécution et la compatibilité réelles avant l'activation ; les paramètres non valides ne mettent pas à jour partiellement le projet et la restauration de l'image conservée préserve la version d'origine et la configuration de l'image.

  • Récupérer les actions Cloud à partir d'instances connectées

    Desktop and self-hosted clients forward Cloud workflow and runner operations to their owning Cloud instance, with the same scope and permission checks.

  • Utiliser la capacité de construction réellement disponible du serveur

    Automatic Cloud builds account for running workloads and pending CPU reservations before choosing their worker size. Build setup also reports the effective workspace capacity.

  • Revérifier l’état du déploiement

    Project status and workload selection reuse current startup-health verification while retaining earlier warnings for review.

  • Suivre les images de conteneurs actuelles pendant les redéploiements de Compose

    Cached Docker inventory preserves immutable image identity, so port preflight and rollback can verify running services safely.

  • Recevoir les modifications en direct dans la boîte de réception

    Webmail refreshes after IMAP IDLE events, with event streams flushed through buffering proxies and correct folder routing.

  • Simplifiez la page de sauvegarde du projet

    The existing project header supplies its title, removing the duplicated backup heading and description.

  • Valider les rôles d'exécution déclarés

    Stack-role configuration rejects missing kinds, empty commands, incomplete exec probes and invalid replica counts. This is configuration/detection support for future role execution.

  • Préserver les domaines qui acheminent uniquement des chemins spécifiques

    Migrations now discover and retain domains with exact or prefix routes and no catch-all service. OpenResty and Cloud routing preserve those paths; unmatched requests return 404. Omitting an existing source catch-all requires a decision before project creation or source container changes. Routing retries keep the previous complete table when a selected upstream is unavailable.

  • Actualiser les images de déploiement avant de remplacer les services

    Manual Docker redeploys refresh mutable registry tags while preserving locally built images and pinned rollback artifacts. Full redeploys keep otherwise unchanged external services, including databases, running when their actual image content matches. Docker validates every replacement image and freezes its reference before activating any service; failed preparation leaves existing containers running. Image preparation is all-or-nothing, while container replacement remains sequential rather than a transaction across the whole stack.