Skip to content
aYOUne
Not in your language

This page is not yet available in en. You're reading the de version.

Upgrades

Upgrades

aYOUne folgt Calendar-Versioning (2026.x.y) und liefert wöchentlich Patches. Self-Hosted-Instanzen bleiben am besten aktuell — Upgrades sind in der Regel zero-downtime, gelegentlich gibt es eine Schema-Migration.

Versions-Strategie

Bestandteil Tempo Beispiel
Patches (2026.x.y) wöchentlich 2026.50.1 → 2026.50.2
Iterationen (2026.x) monatlich 2026.50 → 2026.51
Major-Bumps selten (sehr selten — Plattform ist stabil)

Vor jedem Upgrade lies die Release Notes für deine Spanne.

Compose-Upgrade

ay self-host-update             # interaktiv
ay self-host-update --to 2026.51.0 --backup-first

Was passiert:

  1. Pre-Check — Plattform-Health, License gültig, Disk-Space?
  2. Backup — MongoDB-Dump + Storage-Snapshot
  3. Pull — neue Images (docker compose pull)
  4. Migrate — Schema-Migrations laufen via ay-migration-Container
  5. Restart — Rolling-Restart der Services
  6. Verify — Health-Probes grün?

Bei Fehler im Verify-Step rollt das Tool nicht automatisch zurück, sondern lässt dich entscheiden. Für automatischen Rollback nutze K8s + helm --atomic.

Helm-Upgrade

helm repo update tolinax
helm upgrade --install ayoune \
  tolinax/umbrella \
  --version 2026.51.0 \
  --namespace develop \
  --reuse-values \
  --atomic --wait --timeout 10m

Tipp: Bei umfangreichen Setups Module einzeln upgraden, nicht alle gleichzeitig — schneller und sicherer Rollback bei Fehler.

Schema-Migrations

Größere Änderungen (z.B. Atlas-Index, Collection-Rename, Field-Migration) leben in ayoune-migration. Der Container läuft im Vorfeld:

docker run --rm \
  -e MONGO_URL=$MONGO_URL \
  ghcr.io/tolinax/ayoune-migration:2026.51.0 \
  migrate up --to 2026.51.0

Migrations sind idempotent und nutzen Checksum-Caching — eine bereits gelaufene Migration wird übersprungen. Im K8s-Setup ist das ein Init-Container (umbrella Chart hat ihn eingebaut).

Staged Rollout

Empfohlene Reihenfolge:

  1. Staging zuerst (eigener Namespace / kleinerer Compose-Stack)
  2. Smoke-Test: Login, ein paar CRUDs, Mail-Versand
  3. Production mit --atomic

Best Practice: zwischen Staging und Production mind. 24h liegen, damit Audit-Logs einen Tag voll sind.

Zwischen-Versionen überspringen

Pfad Methode
2026.50.x → 2026.51.x direkt — Patches sind kompatibel
2026.45 → 2026.51 direkt — Iterationen sind aufwärtskompatibel
< 2026.30 → 2026.50+ gestuft — siehe Migration Guide

Sehr alte Versionen (vor 2026.30) brauchen einen Zwischen-Stop, weil zwischen interfaces/models/core große Sprünge liegen.

Rollback

ay self-host-update rollback     # nutzt das letzte automatische Backup
ay self-host-update --to 2026.50.0    # explizit

Bei K8s:

helm rollback ayoune <revision>

Achtung: Rollbacks reverten Code, nicht Daten. Wenn die neue Version Schema-Migrations gefahren hat, brauchst du das Backup aus Schritt 2.

Siehe auch: Troubleshooting, Breaking Changes.

Work with this page

Ready-made instructions for your AI tool. Copy, paste, go — the AI fetches the content itself via the address in the text.

Summarise the steps for me The essentials, in the right order.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/self-hosting/upgrades.md
The complete collection: https://ayoune.com/en/docs/self-hosting.md

Summarise the content for me.

- First, in two sentences: what is this about?
- Then the steps in the order I need to take them.
- One line per step, in plain language.
- At the end: what I should have ready beforehand.

Leave out nothing I need in order to actually finish.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.
Help me set this up Step by step, asking me as you go.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/self-hosting/upgrades.md
The complete collection: https://ayoune.com/en/docs/self-hosting.md

Walk me through the setup step by step.

- First tell me what I need to have ready (access, data, time).
- Then take me through ONE step at a time. Wait for my "next".
- For each step, say how I can tell that it worked.
- If something goes wrong, ask me for the exact message instead of guessing.

If the instructions leave a point open, tell me so rather than inventing it.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.
Help me with a problem Narrow down the cause instead of guessing.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/self-hosting/upgrades.md
The complete collection: https://ayoune.com/en/docs/self-hosting.md

Help me narrow down a problem.

- First ask me what I observe and what I expected instead.
- From that, derive the most likely causes consistent with this source.
- For each cause, give me ONE test that confirms or rules it out.
- Order them so the cheapest test comes first.

Do not guess. If the source does not cover the problem, tell me where I should
look next.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.
Explain it in plain words No jargon, from the ground up.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/self-hosting/upgrades.md
The complete collection: https://ayoune.com/en/docs/self-hosting.md

Explain the content so that someone without prior knowledge understands it.

- Start with the purpose: why does this exist at all?
- Explain technical terms in half a sentence on first use.
- One everyday comparison where it genuinely holds — none where it limps.
- At the end: the three things worth remembering.

Do not shorten by dropping conditions. A simplification that hides a
prerequisite is a false statement.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.
A checklist to tick off To follow along while you do it.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/self-hosting/upgrades.md
The complete collection: https://ayoune.com/en/docs/self-hosting.md

Turn this into a **tick-off checklist** for practical use.

- Exactly one action per item, in the imperative.
- Order it so that no item depends on a later prerequisite.
- Prerequisites and pitfalls as indented sub-items.
- End with an acceptance step: how do I know everything is right?
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.
Build it into my project Concrete code for my use case.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/self-hosting/upgrades.md
The complete collection: https://ayoune.com/en/docs/self-hosting.md

Help me build this into my project.

- First ask me about language, environment and what I am trying to achieve.
- Then give a minimal, runnable example — no ellipses standing in for code.
- Name the error cases I must handle and how they surface.
- State the limits: timeouts, quotas, permissions.

Use only what the source actually describes. Do not invent fields, parameters
or endpoints — an invented call costs me more time than it saves.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.

Was this article helpful?

👎 No (0)
Leave a comment