26 lines
2.1 KiB
Markdown
26 lines
2.1 KiB
Markdown
# ForgeFlow 0.9.3
|
|
|
|
This release removes server-side repository authentication from every SSH/Unraid deployment path and makes server Compose files the primary discovery source.
|
|
|
|
## Direct deployment only
|
|
|
|
- Every existing SSH/Unraid deployment profile is migrated to **Direct copy**, except profiles explicitly marked **Monitor only**.
|
|
- Deployment and rollback archive the exact committed local HEAD, upload it over the already configured desktop-to-Unraid connection and run Docker Compose on Unraid.
|
|
- Preflight contains no Unraid-to-repository access probe, no remote `git ls-remote`, no repository-key validation and no Git requirement on Unraid.
|
|
- Password authentication for the desktop-to-Unraid connection remains supported and is independent of repository access.
|
|
|
|
## Compose-file inventory and automatic linking
|
|
|
|
- Server Inventory scans Compose YAML files such as `compose.yml`, `compose.yaml`, `docker-compose.yml`, `docker-compose.yaml`, overrides and stack YAML files below the configured appdata roots.
|
|
- YAML discovery still runs when Docker inspection fails or Docker is unavailable, so a container-query problem no longer produces a false empty inventory.
|
|
- ForgeFlow reads the Compose project name, file set, service names and image names from the server.
|
|
- A unique high-confidence repository match based on both Compose folder and project identity is linked automatically.
|
|
- Remaining strong matches use a one-click link action with server folder, Compose project, Compose files, services, container identity and preservation paths already filled in.
|
|
- Runtime containers, stopped containers and DockerMan templates are merged with the YAML definition when available. `/mnt/user/appdata`, `/mnt/cache/appdata` and disk-backed appdata paths are treated as the same logical deployment location.
|
|
|
|
## Reliability
|
|
|
|
- The inventory shell script is safe under `set -euo pipefail`; Docker or Compose command failures are captured as warnings instead of aborting the scan.
|
|
- Large runtime, cache, log and database folders are pruned while searching for Compose files.
|
|
- A failed inventory operation remains visible as an error and is never presented as zero workloads.
|