fix(oci): say where the converter entry point has to run

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>
This commit is contained in:
MacRimi
2026-09-22 23:13:28 +02:00
co-authored by Claude Opus 5
parent 13ad61e8b0
commit 41b999ffeb
2 changed files with 19 additions and 1 deletions
+1 -1
View File
@@ -2,7 +2,7 @@
Runtime distribution only:
- `proxmenux-oci.sh`: installer entry point.
- `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.