Files
ProxMenux/oci/PACKAGE-CONTENTS.md
T
MacRimiandClaude Opus 5 f3bda28338 refactor(oci): remove the shell entry point nothing runs
`oci/proxmenux-oci.sh` was installed on every Proxmox host and used on
none of them. The menu entry goes straight to the orchestrator:
scripts/oci/oci_manager_apps.sh runs `python3 -m proxmenux_oci` with
PYTHONPATH pointing at the engine.

Its only remaining caller was a message telling the reader to open it on
the Proxmox host — which is not how anyone gets in, and is what sent one
there to run it. That message now names the menu entry.

It could not be fetched and run either: it needs requirements.txt and
src/ beside it, so `wget | bash` resolved its own directory to the
working directory and failed on a path nobody chose. Making that work
would mean writing a second installer next to the one that already
ships the engine.

What it did offer was a virtualenv for a contributor generating the
catalog. The README now gives the direct invocation and names the two
distribution packages it needs.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-22 23:22:51 +02:00

506 B

ProxMenux OCI package

Runtime distribution only:

  • 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.