Cloudron Forum

Hi everyone

I’d like to share a first functional draft of GLPI 11 packaged for Cloudron.
It’s not a finished or “official” package yet, but the foundation is already solid and clean, and follows Cloudron best practices.

Git repository:
https://github.com/vitetj/Cloudron-GLPI

Current state

GLPI 11.x

MySQL via Cloudron addon

Persistent data stored in /app/data

Intentional manual installation via CLI script (for safety and clarity)

Cloudron post-install message (red warning box) to guide admins

Idempotent initialization script (init-glpi.sh)

Clean start.sh with no hidden automation

The goal was to build something that is:

admin-friendly

maintainable

Cloudron-native

explicit rather than “magic”

What’s coming next

I plan to continue improving the package with:

GLPI cron tasks (via Cloudron Cron)

Cloudron SMTP integration

LDAP / SSO

additional hardening and cleanup

better admin documentation

This is very much a work in progress, but I wanted to share early to get feedback from the Cloudron community, especially on:

the installation flow

the manual post-install approach

the overall package architecture

Any feedback is welcome

Technical update: LDAP authentication is now working.

The fix was to move the whole LDAP setup into start.sh and make it fully deterministic:
• wait for the MySQL service to be reachable
• inject the LDAP configuration directly into glpi_authldaps using Cloudron-provided env vars
• clear GLPI cache
• run an explicit ldap:sync

This avoids init-time race conditions and inconsistent behavior observed with glpi:ldap:create alone.
Current repo reflects the working implementation.

edit : My bad i just fix the marketplace directory permissions with symlink to persistent storage
Should be ok now

Main Page: https://github.com/aloks98/isoman

Cloudron Git (Fork): https://github.com/vitetj/Cloudron-isoman

Licence: MIT (original project)

Dockerfile: Yes (adapted for Cloudron)

Demo: Not available

Summary:
IsoMan is a lightweight web application designed to manage ISO files and system images in self-hosted environments.

It provides a simple web interface to upload, organize, and access ISO images from a centralized location. This is particularly useful for system administrators managing virtualization platforms (VMware, Proxmox, Hyper-V), lab environments, or infrastructure where ISO files are frequently used for deployments and recovery.

I did not develop the original application — it was created by @aloks98. I forked the project and adapted it to run properly on Cloudron by containerizing and adjusting it to meet Cloudron packaging requirements.

The application is minimal, practical, and fits well within the self-hosted ecosystem.

Key features:

Web-based ISO file management

Centralized ISO repository

Lightweight and simple interface

Docker-based deployment

Easy integration in self-hosted infrastructure

Notes:
I believe this is an interesting addition to Cloudron because:

Many Cloudron users run home labs or small infrastructure setups

ISO management is still often handled manually via NAS shares or file browsers

This provides a dedicated, clean interface for ISO storage

The app is lightweight and does not require complex dependencies

The Cloudron adaptation ensures:

Proper containerization

Persistent storage handling

Compatibility with Cloudron’s app packaging model

Possible future improvements (upstream or fork):

Role-based access control

Checksum verification

API access

Better UI enhancements

Alternative to / Libhunt link:
There is no direct equivalent lightweight ISO manager in the Cloudron ecosystem.
It can be seen as an alternative to manually managing ISO files via shared folders or generic file managers.

@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

@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

thank you — in GLPI you can fully configure authentication directly via the CLI, since all auth settings are stored in the database.

The idea is simply to inject the configuration at install time, during the app initialization phase, instead of doing anything in the GUI.

In a Cloudron context, that means:
• Enable the ldap addon in CloudronManifest.json
• Let Cloudron inject the LDAP environment variables
• Use the GLPI CLI (bin/console) to create and enable the LDAP directory
• Do all of this inside the init script, once the database is ready

Example of what I’m planning to wire into init-glpi.sh:

php bin/console glpi:ldap:create
--default
--active
--name="Cloudron LDAP"
--host="${CLOUDRON_LDAP_URL#ldap://}"
--port=389
--basedn="ou=users,${CLOUDRON_LDAP_BASE_DN}"
--rootdn="${CLOUDRON_LDAP_BIND_DN}"
--rootdn-pass="${CLOUDRON_LDAP_BIND_PASSWORD}"
--login-field="username"
--email-field="mail"
--firstname-field="givenName"
--realname-field="sn"
--use-tls=0

This config is written directly to the GLPI database, so no UI interaction is required.

I haven’t tested this end-to-end yet — I’m a bit short on time this week — but from GLPI’s CLI and schema, this should be the correct approach. I’ll validate and clean it up when I have more bandwidth.

@girish said in GLPI - Asset and IT Management Software:

@vitetj great stuff! I have asked @vladimir.d to look into this so we can get it published. Was there a reason to use LDAP and not OIDC ? https://help.glpi-project.org/doc-plugins/oauthsso ? Also, if we may reuse your work, can you please put in a LICENSE file at https://github.com/vitetj/Cloudron-GLPI ? Any opensource license (MIT, GPL etc) will work.

Hey — thanks!

On OIDC: the plugin you linked (oauthsso) is not free (it’s available through a GLPI subscription / GLPI Network), which is why I went with LDAP for a default setup.

That said, OIDC is definitely on my todo list. There are community/free options we can build on for OIDC SSO, for example:
https://github.com/edgardmessias/glpi-singlesignon

And yes — happy to help with reuse: I’ll add a LICENSE file to https://github.com/vitetj/Cloudron-GLPI so it can be published/used properly.

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

@nebulon Thanks, it’s my pleasure!
Thank you as well for the quick analysis and publication — great work!

@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!