MACHINES CHANGE.KEEP YOUR BEARINGS.
Record Arch Linux packages, configuration and services in Git, compare changes and prepare to restore an environment.
See how it works ↓In development
An animated explanation of snapshots and restoration.
01 / IN MOTION
From a machine’s state to its history.
02 / The starting point
Keep a memory of a Linux environment.
Packages, configuration and services evolve with use. Reconstructing an environment starts with knowing what changed.
03 / What it brings together
- 01Capture packages, configuration and services.
- 02Compare the current state with a recorded state.
- 03Prepare restoration from Git history.
04 / Under the interface
- The constraint
- Distinguish a state recorded in Git from operations that actually change the machine.
- The decision
- Phoenix separates configuration history from actions affecting the system. Returning to a snapshot in the repository and applying it to the machine are distinct operations.
Restoration starts with a state you can understand: what was captured, what changed and what you want to recover.
05 / What this explores
Separating history from system changes.
Inventory, comparison and understandable system operations: an approach for environments that need to be reproduced.
Project status & presentation scope
Personal tool in development. Capture, comparison and restoration exist in the code; no real machine restoration was performed for this presentation.