Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Offical apps | Community apps | Demo | Docs | Install
vitetjV

vitetj

@vitetj
App Dev CA Maintainer
Unfollow Follow
About
Posts
19
Topics
3
Shares
0
Groups
2
Followers
0
Following
0

Posts

Recent Best Controversial

  • MeshCentral
    vitetjV vitetj
    Community Packages

    @paramedicspecialist Thanks for packaging this! I’ll definitely give the Cloudron package a try.

    @joseph Just to add some context about MeshCentral: it’s actually quite a bit more powerful than a simple remote desktop tool. It’s a long-standing open-source remote management project, originally developed with strong Intel involvement, particularly around Intel AMT/vPro.

    I personally use MeshCentral in production to manage around 300 devices across 3 countries.

    With the regular MeshAgent, you can remotely access desktops, terminals and files, run commands/scripts, manage devices, and tunnel protocols such as RDP or SSH.

    Where it gets especially interesting is with Intel vPro/AMT hardware. You can get true out-of-band management: remotely power a computer on/off, reboot it, access hardware KVM, boot to BIOS or another boot device, etc. This can work independently of the operating system — even when the machine is powered off, as long as AMT remains powered and reachable.

    So while it’s not a full RMM in the same sense as products with integrated patch management, MeshCentral can be a very capable self-hosted management platform, especially when combined with scripts or another software deployment/patching solution.

    Really happy to see it packaged for Cloudron!


  • Odoo 20 on cloudron
    vitetjV vitetj
    Community Packages

    Odoo (community package) 20.0.2 - security update for the PHP RCEs (CVE-2026-109618 / CVE-2026-109619)

    Package: Odoo 20 for Cloudron (com.vitetj.odoo)
    Repo: https://github.com/vitetj/cloudron-odoo
    Install URL (App Store → Community apps): https://raw.githubusercontent.com/vitetj/cloudron-odoo/main/CloudronVersions.json

    What changed

    • Base image moved from cloudron/base:5.0.0 to cloudron/base:5.1.0 (still Ubuntu 24.04).
    • cloudron/base:5.0.0 bundles PHP 8.3, which is affected by the critical unauthenticated RCEs CVE-2026-109618 / CVE-2026-109619 (CERT-EU advisory 2026-018). Odoo is Python and never used that PHP, but the vulnerable interpreter was still present in the container. cloudron/base:5.1.0 no longer ships PHP at all.
    • The Dockerfile now fails the build if a PHP interpreter or any php* package ever reappears in the image.
    • No functional change to Odoo itself (still nightly 20.0.20260926).

    Upgrading

    Existing installs pick up 20.0.2 through the normal update check. The update is a plain image swap: no data migration, Odoo does not run -u all since the Odoo release is unchanged.

    Note for other packagers

    Any community package still built on cloudron/base:5.0.0 carries PHP 8.3 even if the app does not use PHP. Switching to cloudron/base:5.1.0 (no PHP, Ubuntu 24.04) or 6.0.1 (Ubuntu 26.04) removes it; apps that do need PHP should move to cloudron/php-base:8.5-20261021 or 8.4-20261021.

    References:

    • https://cert.europa.eu/publications/security-advisories/2026-018/
    • https://forum.cloudron.io/topic/15806/new-base-image-5.1.0
    • https://github.com/vitetj/cloudron-odoo/pull/1

  • Odoo 20 on cloudron
    vitetjV vitetj
    Community Packages

    @james yes i did 🙂
    https://ca.cloudron.io/app/odoo


  • Odoo 20 on cloudron
    vitetjV vitetj
    Community Packages

    Hi everyone! 👋

    I've been working on updating the existing Odoo package for Cloudron, originally developed by @njsubedi.

    I'm happy to share my fork, which brings Odoo 20 to Cloudron! 🚀

    GitHub repository:
    https://github.com/vitetj/cloudron-odoo

    What's included?

    • Odoo 20, based on the official Odoo nightly packages
    • Cloudron base image 5.0.0 (Ubuntu 24.04)
    • PostgreSQL integration
    • Cloudron LDAP authentication
    • Email integration (sendmail and recvmail)
    • WebSocket support for live chat
    • Support for custom Odoo modules
    • Automatic module updates when upgrading the package
    • Installation through Cloudron Community Apps

    Installation

    You can install it directly from the Cloudron dashboard:

    App Store → Community Apps → Add

    Use the following URL:

    https://raw.githubusercontent.com/vitetj/cloudron-odoo/main/CloudronVersions.json

    Community feedback welcome!

    This is a community-maintained package, not an official Cloudron application.

    I'd love to hear your feedback, especially regarding installation, compatibility, upgrades, and potential improvements.

    Feel free to open issues or contribute directly on GitHub.

    Hopefully, this will help bring Odoo one step closer to becoming an officially supported Cloudron application!

    Cheers,


  • Odoo - distributed business apps
    vitetjV vitetj
    App Wishlist

    Hi everyone! 👋

    I've been working on updating the existing Odoo package for Cloudron, originally developed by @njsubedi.

    I'm happy to share my fork, which brings Odoo 20 to Cloudron! 🚀

    GitHub repository:
    https://github.com/vitetj/cloudron-odoo
    Community app :
    https://ca.cloudron.io/app/odoo

    What's included?

    • Odoo 20, based on the official Odoo nightly packages
    • Cloudron base image 5.0.0 (Ubuntu 24.04)
    • PostgreSQL integration
    • Cloudron LDAP authentication
    • Email integration (sendmail and recvmail)
    • WebSocket support for live chat
    • Support for custom Odoo modules
    • Automatic module updates when upgrading the package
    • Installation through Cloudron Community Apps

    Installation

    You can install it directly from the Cloudron dashboard:

    App Store → Community Apps → Add

    Use the following URL:

    https://raw.githubusercontent.com/vitetj/cloudron-odoo/main/CloudronVersions.json

    Community feedback welcome!

    This is a community-maintained package, not an official Cloudron application.

    I'd love to hear your feedback, especially regarding installation, compatibility, upgrades, and potential improvements.

    Feel free to open issues or contribute directly on GitHub.

    Hopefully, this will help bring Odoo one step closer to becoming an officially supported Cloudron application!

    Cheers,


  • 🚀 Documize Conversion: community package for Documize's Word import / PDF export service
    vitetjV vitetj
    Community Packages documize conversion documents pdf word

    @joseph here we go ! https://ca.cloudron.io/app/documize-conversion


  • 🚀 Documize Conversion: community package for Documize's Word import / PDF export service
    vitetjV vitetj
    Community Packages documize conversion documents pdf word

    Documize Community delegates two things to a separate service: Word document import and PDF export. Out of the box it points at Documize's shared hosted endpoint, and upstream recommends self-hosting the documize/conversion container instead and changing the conversion endpoint URL to your own.
    So here it is as a Cloudron app. No UI, no login — it just answers the API calls your Documize instance makes.

    image-1790062294772.png
    Repo: https://github.com/vitetj/documizeconversion-cloudron
    Upstream version: 3.4.0

    Install

    App Store → Install from URL:
    https://raw.githubusercontent.com/vitetj/documizeconversion-cloudron/main/CloudronVersions.json

    or:
    cloudron install --versions-url https://raw.githubusercontent.com/vitetj/documizeconversion-cloudron/main/CloudronVersions.json --location conversion --domain example.com

    Then, in Documize as an administrator, set the conversion endpoint to the app's origin. That's the whole setup.
    Check it is alive with curl https://<app-domain>/api/version → 3.4.0.

    Packaging notes

    Upstream publishes no source release, only the Docker image, so the Dockerfile lifts the artifacts out of documize/conversion:3.4.0 and re-assembles them on cloudron/base:5.1.0: the Go API binary, the Aspose/PlantUML jars (run with OpenJDK 11 from the Ubuntu archive), puppet.js + node_modules with the Chromium puppeteer bundles, and the upstream TrueType fonts — without those, Word→PDF layout drifts.
    Two upstream quirks shaped the start script, in case they help anyone packaging something similar:

    • the API binary resolves java/ and puppet.js relative to its working directory and writes a log there, so it can't run from the read-only /app/code — it starts from a writable /run/documize that symlinks the code;
    • its scratch directory follows TMPDIR, pointed at /app/data/tmp, because a large .docx would blow through the small /tmp tmpfs.
      Other details: httpPort 5010, health check /api/version, localstorage addon, runs as cloudron (never root), memoryLimit 2 GB because Word conversion spawns a JVM with -Xmx1000m on top of Chromium. The image is ~3.6 GB, mostly fonts and the bundled Chromium.

    Heads up: the API is unauthenticated

    That's how the upstream service works — Documize calls it server-to-server with no credentials, so the package can't put SSO or proxyAuth in front of it without breaking it. Anyone who knows the domain can submit a document for conversion. If the endpoint doesn't need to be public, restrict it at the firewall to your Documize server's IP.

    Tested

    Health check, a real .docx converted through POST /api/1/word (the Aspose/Java path), PDF rendering with the bundled Chromium as the cloudron user, and a restart with existing app data. Feedback and issues welcome on the repo.


  • IsoMan on Cloudron – ISO Image Management Made Simple
    vitetjV vitetj
    App Wishlist

    @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


  • IsoMan on Cloudron – ISO Image Management Made Simple
    vitetjV vitetj
    App Wishlist

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


  • IsoMan on Cloudron – ISO Image Management Made Simple
    vitetjV vitetj
    App Wishlist

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


  • IsoMan on Cloudron – ISO Image Management Made Simple
    vitetjV vitetj
    App Wishlist

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


  • IsoMan on Cloudron – ISO Image Management Made Simple
    vitetjV vitetj
    App Wishlist

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


  • IsoMan on Cloudron – ISO Image Management Made Simple
    vitetjV vitetj
    App Wishlist

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


  • IsoMan on Cloudron – ISO Image Management Made Simple
    vitetjV vitetj
    App Wishlist

    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.


  • GLPI is now available
    vitetjV vitetj
    Announcements

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


  • GLPI - Asset and IT Management Software
    vitetjV vitetj
    App Wishlist

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


  • GLPI - Asset and IT Management Software
    vitetjV vitetj
    App Wishlist

    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 🙂


  • GLPI - Asset and IT Management Software
    vitetjV vitetj
    App Wishlist

    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.


  • GLPI - Asset and IT Management Software
    vitetjV vitetj
    App Wishlist

    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 👍

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search