23 lines
1.2 KiB
Markdown
23 lines
1.2 KiB
Markdown
# ForgeFlow 0.8.7
|
|
|
|
ForgeFlow 0.8.7 automatically discovers applications already running on every
|
|
configured and trusted Unraid server. It inventories server-side Git checkouts,
|
|
Docker Compose metadata, bind mounts, container identity and image provenance,
|
|
then links each workload to a Gitea repository only when the evidence produces
|
|
one unambiguous match.
|
|
|
|
Uniquely matched workloads are added to Deployments automatically, even when
|
|
they were originally deployed outside ForgeFlow. Every refresh resolves the
|
|
configured branch directly on Gitea and compares its full commit SHA with the
|
|
live server version. A deployment is reported as in order when the SHAs match,
|
|
the container is running and Docker health is not failing.
|
|
|
|
Containers without a server-side Git checkout can also be discovered when the
|
|
image exposes standard OCI source/revision labels or ForgeFlow provenance
|
|
labels. New ForgeFlow deployments now write repository, branch and exact commit
|
|
labels so future discovery remains deterministic.
|
|
|
|
Ambiguous or weak matches are intentionally left unlinked for manual review.
|
|
Server inventory is read-only; automatic adoption changes only ForgeFlow's local
|
|
configuration.
|