maggesandClaude Sonnet 5
e2fefcdf9c
- versions.env pins podman, conmon, crun, netavark, aardvark-dns, passt, and fuse-overlayfs to verified upstream source checksums; SlackBuild recipes, scripts/build-packages.sh, checksums.sh, release.sh, and update-versions.sh implement the reproducible pipeline; GitHub Actions workflows build in a Slackware container and publish releases without committing any binaries. - plugin/podman.plg installs/updates/removes all eight packages (the seven components plus the plugin's own unraid-podman scaffolding package) via upgradepkg, using the official Unraid array-event hook mechanism (event/disks_mounted, event/stopping) instead of editing /boot/config/go. rc.podman and the sbin/ helper scripts implement storage creation, config seeding/sync, preflight checks, autostart with per-container Safe-Mode, and package verify/update/rollback. - webui/plugins/podman implements the Dashboard, Containers, Pods, Images, Volumes, Networks, Logs, Terminal, Compose, and Settings panels against the approved mockup (webui/mockups/prototype.html), talking to podman system service exclusively via PodmanClient.php (libpod REST API over the Unix socket), with two documented exceptions: Terminal's one-shot exec model and Compose's use of the podman compose CLI, since libpod has no REST equivalent for either. - docs/ARCHITECTURE.md and docs/ROADMAP.md record the design decisions and honest current status (syntax-checked, unit- and integration-tested against fake sockets/servers; not yet run against a real Unraid/Podman/Slackware system). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
26 lines
1.3 KiB
Bash
Executable File
26 lines
1.3 KiB
Bash
Executable File
#!/bin/bash
|
|
# =============================================================================
|
|
# plugin/event/disks_mounted
|
|
#
|
|
# Official Unraid plugin event hook — NOT a custom mechanism. Unraid's
|
|
# emhttpd fires every executable found at
|
|
# /usr/local/emhttp/plugins/<name>/event/<eventname> as each boot/array
|
|
# event happens (see e.g. the real-world unassigned.devices plugin, which
|
|
# uses this same convention for its own disks_mounted/started/stopping_svcs
|
|
# hooks). This project relies exclusively on this official mechanism —
|
|
# specifically NOT on hand-editing /boot/config/go, which is unnecessary
|
|
# and easy to get wrong across plugin updates/uninstalls.
|
|
#
|
|
# "disks_mounted" fires once array disks AND cache pools are mounted —
|
|
# exactly the precondition unraid-podman needs before it can create/mount
|
|
# podman.img on the configured cache pool/disk (see
|
|
# docs/ARCHITECTURE.md section 4.3 and section 6.2).
|
|
#
|
|
# Backgrounded (& disown) so array startup / the Main GUI page isn't
|
|
# blocked on podman's full startup sequence (preflight, storage mount,
|
|
# service start, autostart chain) — mirrors how unassigned.devices
|
|
# backgrounds its own longer-running "started" hook.
|
|
# =============================================================================
|
|
|
|
/etc/rc.d/rc.podman start > /dev/null 2>&1 & disown
|