Zum Inhalt springen
Produkte

// Benutzung · Konfiguration & Rollback

Viewing a location's config history

Every change you make to a location — its settings, and the resources under it — is recorded automatically. You never have to turn this on.

Where to find it

Open a location (Locations → pick one). Below its resources is a Config history section with two parts:

  • Safe checkpoints — named restore points you (or a teammate) marked as known-good. These are shown as distinct, highlighted cards.
  • The timeline — the automatic, per-change history beneath them, newest first.

Reading the timeline

Each entry shows what changed and how:

  • the kind of thing (location or resource) and its name,
  • the action — created, updated, deleted, or restored,
  • who made the change, and when.

Deletions and rollbacks are marked distinctly, so a restore is visible as its own event — a rollback never erases what came before it.

What's covered

The history tracks the things you configure through the platform: the location's own settings and the resources you register by hand. Auto-discovered sub-resources (VMs, pods, nodes that Fleeger finds on its own) are not in the history — they refresh from the live source every cycle. That includes your own changes to them: giving a discovered resource its own name and tags (Name and tags on its card), or attaching or detaching its credential, is not recorded, and a rollback does not undo it. Discovery keeps your own name and tags; the name and tags the source reports stay beside them, refreshed every cycle. Entries for discovered resources written by earlier versions stay listed, and rollbacks ignore them.

To turn a good state into a restore point, see Creating a safe checkpoint.

// Zusammenarbeit

Bereit, Ihre digitale Infrastruktur zu bauen?

Ob individuelle Automatisierung für Ihr Unternehmen oder ein durchgeplantes Netzwerk für Ihr Zuhause — lassen Sie uns über das Projekt sprechen.