mirror of
https://github.com/MacRimi/ProxMenux.git
synced 2026-09-29 18:16:43 +00:00
MacRimiandClaude Opus 5
41b999ffeb
Fetched with wget and piped to bash, $0 is "bash" and the script resolves its own directory to wherever the shell happens to be. It then reports "shasum: /root/requirements.txt: No such file or directory", which names a path the reader never chose and says nothing about the real problem. It now checks for the files it needs and names both places it runs from: the installed engine directory on a Proxmox host, or oci/ in a clone. PACKAGE-CONTENTS.md called it the "installer entry point", which is what invites fetching it over the network in the first place. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
566 B
566 B
ProxMenux OCI package
Runtime distribution only:
proxmenux-oci.sh: entry point, run from this directory.catalog/: index, application templates, curated definitions and overlays.src/: menu and deployment orchestrator.remote/: native Proxmox OCI/LXC installation and lifecycle helpers.schemas/: catalog schema.requirements.txt: Python dependencies.README.md: operational documentation.
Development-only tests, virtual environments, laboratory evidence, caches and legacy root-level *-oci.json files are intentionally excluded.