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>
plugin/boot-config/plugins/podman/
This directory is a staged mirror of what /boot/config/plugins/podman/ should
look like immediately after a first install — see
docs/ARCHITECTURE.md, section 4.1.
The .plg postinstall step (see plugin/podman.plg) copies these files to
/boot/config/plugins/podman/ only if they don't already exist, so
re-running an install/update never clobbers a user's existing configuration.
Config file content templates (containers.conf, storage.conf,
registries.conf, policy.json) are sourced from the top-level config/
directory rather than duplicated here — this directory only defines the
directory skeleton and the plugin-specific settings files (podman.cfg,
autostart, ...) that have no equivalent elsewhere.
plugins/podman/
├── podman.cfg # copied from config/podman.cfg.example
├── autostart # empty by default, see docs/ARCHITECTURE.md section 12
├── autostart-delay # empty by default
├── networks/ # empty, populated as custom networks are created
├── backup/
│ ├── packages/ # empty, populated on first update
│ └── config/ # empty, populated on first update
└── plugin.log # empty, install/update log