Skip to content

Document a safe upgrade procedure (backup + verify + rollback) #4

Description

@shanzez

Problem

The README's "Updating" section and MIGRATION.md cover the mechanics of bumping versions, but there is no single runbook that walks an operator through a safe upgrade end to end - in particular taking a backup first, verifying afterwards, and rolling back if it fails. This is the most common self-host question upstream:

  • huly-selfhost#221 - How can I upgrade huly-selfhost?
  • huly-selfhost#91 - How can I upgrade the Huly version?
  • huly-selfhost#51 - Updating via Issue Board

Proposal

Add guides/upgrading.md: review MIGRATION.md -> backup -> stop -> pull -> set version -> pull images -> up -> verify -> rollback. Link it from the README's Updating section. Pairs with the Compose backup/restore work in #1.

A PR follows. Contributed by Exaviz (exaviz.com).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions