Repository navigation
Simplify Compose installation and add a reproducible memory tutorial - #90
Merged
Merged
Conversation
decryptus
marked this pull request as ready for review
October 9, 2026 09:38
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The repository root still starts an old cron example with broad automatic actions and the unmaintained
latesttag. That makes it a poor default installation and a confusing starting point for a tutorial.This change makes the root Compose an observation-only agent and adds an optional UI overlay that reuses the existing authenticated UI service. The separate Prometheus/Grafana stack remains the advanced path. Agent and UI examples use verified published 1.1.1 images.
A disposable memory lab adds a bounded worker, explicit target selection, a dry-run walkthrough, sustained threshold, cooldown, one-attempt restart budget, audit exports and cleanup. Automatic actions require explicitly selecting the demo-guard scenario. The FR/EN quickstarts explain the changed behavior for existing root cron users.
Validation completed locally:
Docker was unavailable locally, so the new CI acceptance job exercised the actual root stack on a disposable Docker runner. It passed for commit b57bb03: minimal API access, authenticated UI, real memory growth, dry run without restart, automatic restart, recovery through the UI, exhausted restart budget, memory release and retained journal after down/up.
The first acceptance run caught an unreachable host port on an internal bridge. The root agent now uses a normal bridge and keeps its published API port bound to 127.0.0.1. The standalone UI example still uses its private internal agent network with no published agent port.
Both GitHub workflows passed on this commit:
Existing acceptance also passed for the advanced monitoring stack, UI, Python distributions, Docker image, upgrades, terminal and notifications.
No package version change or deployment is included.