-
26.19-alpha
Pre-releaseAll checks were successfulBuild ISO / build-iso (push) Successful in 19m56sDeploy site / deploy (push) Successful in 4sCI / lint (push) Successful in 23sCI / test (push) Successful in 1m18sCI / validate-json (push) Successful in 21sCI / markdown-links (push) Successful in 13sRelease / release (push) Successful in 12m36sreleased this
2026-08-23 16:05:43 +02:00 | 0 commits to main since this releaseFixed
- App installs now copy subdirectories, so dependency hooks actually
ship.install_from()only copied an app's top-level files, so the
scripts/folder — where a provider'son_install/on_startdependency
hooks live — never reached/var/lib/furtka/apps/<app>/, and every hooked
dependency failed at reconcile withhook ... missing in provider. The
whole app folder is copied now (rmtree+copytree, so a reinstall also
drops files that were removed upstream). Found during the first real
end-to-end run of the mosquitto + zigbee2mqtt pair on a test VM. furtka app install <name>now runson_installhooks. Named CLI
installs copied the app folders and then ran a bare reconcile, which fires
on_startbut neveron_install— so a CLI install of a consumer brought
its provider up without ever provisioning it (no account created, empty
MQTT_*values in the consumer's.env). Named installs now go through
install_runner.run_install(writing the plan file first), the same docker
phase the API dispatches, so providers come up before consumers and
on_installhooks run. Path-based installs keep the copy + reconcile
dev/test path.
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
-
furtka-26.19-alpha.iso
1 download · 1.5 GiB
-
furtka-26.19-alpha.tar.gz
2 downloads · 72 KiB
-
furtka-26.19-alpha.tar.gz.sha256
2 downloads · 92 B
-
release.json
2 downloads · 173 B
- App installs now copy subdirectories, so dependency hooks actually