IsoMan on Cloudron – ISO Image Management Made Simple

[vitetj]

@robi @timconsidine Thanks for the feedback

The Docker image is publicly available here:
https://hub.docker.com/r/vitetj/isoman

If needed, you can also build directly from the Git repository and deploy the traditional
https://github.com/vitetj/Cloudron-isoman
Cloudron way:
• Cloudron build
• Cloudron install

This works on our servers without issue.

Let me know if CCAI-P requires a specific packaging format or deployment method.

[james]

Hello @vitetj
With Cloudron 9.1 we have added community app support.
Please see: https://docs.cloudron.io/packaging/publishing/

[vitetj]

@james Hi,

Thanks for the info! My server isn’t updated to 9.1 yet, but I’ll take a look at the documentation and update my Git repository accordingly once I’ve upgraded

Appreciate the heads-up!

[vitetj]

@robi @james @timconsidine

Morning on my side

Here we go:
https://raw.githubusercontent.com/vitetj/Cloudron-isoman/master/CloudronVersions.json

It’s working for me

[nebulon]

Great, installs well, was able to add some ISOs but otherwise have no real use-case for this

[joseph]

If you can add the proxyAuth addon, then one can secure the instance .

[vitetj]

@joseph I tried implementing the proxyAuth addon, but I wasn’t able to properly sync it with OIDC or LDAP.

The only way I managed to make it work was with a static login defined via environment variables stored in the app data. I’m not really comfortable with that approach, so I rolled it back for now

I’m going to study the original project more deeply to see if I can implement a proper unique token mechanism for downloads instead. I’m not a big fan of keeping secrets in a file.

[james]

Hello @vitetj
With proxyauth in the manifest it should work out of the box.
No extra configuration needed.

---

EDIT:
Now I see that IsoMan has the option to enable LDAP auth but is not enabled or configured on app installation.
The best route would be to set up the LDAP auth from the IsoMan app itself for the Cloudron Community app.

Another thing I noticed.
Since the app does not build on the cloudron base image, many expected defaults are missing or simply broken.
The Web Terminal is not working at all.
There is no way to add environment variables in /app/data/ to further configure the app according to e.g.: ENV.md

[vitetj]

@james Thanks for the feedback!

I’m going to rebase the project on a proper Cloudron base image — that will definitely make things simpler and align with the expected defaults.

Indeed, the current version you’re seeing isn’t really suitable. It was more of a local development build from my PC

I’ll work on a cleaner image based on the official deployment guide and adapt it for Cloudron:
https://github.com/aloks98/isoman/blob/master/docs/DEPLOYMENT.md

I’ll keep you posted once I have a proper build ready.

[vitetj]

@james Quick update — I just shipped a full Cloudron-native refresh of ISOMan (v0.3.8).

This version is now properly aligned with Cloudron expectations and based on a cleaner packaging approach.

Key updates:

• Cloudron packaging aligned for production: proxyAuth + LDAP addons, persistent /app/data, internal port 8080, and healthcheck at /api/health.
• Added optional create-only protection for POST /api/isos with LDAP-first authentication (Basic fallback still supported).
• Fixed frontend create-flow issues when auth challenges returned HTML/non-JSON responses.
• Added credential prompt handling for create-only auth and improved dialog accessibility.
• Updated app icon handling for Cloudron login compatibility (PNG).
• Deployment docs refreshed and fully translated to English.

Result:

Global access control remains managed by Cloudron proxyAuth, while ISO creation can now be protected independently without breaking the normal read/list UX.

0084e5c9-7ebf-440e-8746-d338bd190680-image.jpeg