@andreasdueren You're right, thanks for spotting. I tested it on a live install: with server.stuns pointing at Cloudron's STUN (CLOUDRON_TURN_SERVER:CLOUDRON_TURN_PORT). NetBird switches off its own STUN, clients report Cloudron's STUN as available, peers connect, and NetBird's own relay keeps running. The new release uses Cloudron's STUN by default, so new installs won't need an extra UDP port or clash on 3478. LMK if it works for you.

Self-Hosted RustDesk Configuration for MiroTalk SFU (Cloudron) Docker image build in progress... MiroTalk SFU v.2.6.14 Configure the following environment variables in your MiroTalk SFU env file to use your own RustDesk server hosted on Cloudron: # Enable presenter remote control requests (true|false) REMOTE_CONTROL_ENABLED=true # Allow public access to the setup page. # true = anyone with the URL can access it # false = access requires a valid token from a MiroTalk room request REMOTE_CONTROL_DOWNLOAD_URL_PUBLIC=false # Leave it empty here REMOTE_CONTROL_DOWNLOAD_URL= # RustDesk ID server hostname (e.g. rustdesk.example.com) REMOTE_CONTROL_SERVER_HOST= # RustDesk server PUBLIC key (contents of id_ed25519.pub) # Never use or expose the private key (id_ed25519). REMOTE_CONTROL_SERVER_KEY= How It Works By default, REMOTE_CONTROL_SETUP_PUBLIC=false, so access to the setup page requires a valid, room-bound token. The presenter sends a remote-control request to a participant. When the request is created, the server generates a signed token bound to the room, valid for 15 minutes. The participant receives a Get RustDesk link pointing to /remote-control/setup?t=<token>. The setup page validates the token. Requests with missing, invalid, forged, or expired tokens return 404 Not Found. Optional: Public Setup Page Set REMOTE_CONTROL_SETUP_PUBLIC=true to make the setup page publicly accessible without a token. Anyone with the URL can open it. Security recommendation: Keep REMOTE_CONTROL_SETUP_PUBLIC=false to ensure setup links are time-limited and tied to the relevant room. This protects access to the setup page, while RustDesk relay security must still be configured separately.

ok, we now have: https://ca.cloudron.io/app/io.github.ravolar.cap https://ca.cloudron.io/app/io.ente.cloudronapp Conflicting titles - https://ca.cloudron.io/app/cap [image: image.jpeg]

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,

@girish It was about this feature request. And while you're at it, please also deploy this one, it's messing with my workflow

With Cloudron 10.1 released i could finally test the healtchecks app I created a few weeks ago: https://ca.cloudron.io/app/healthchecks The app is integrated into the Cloudron user management via ProxyAuth which required 10.1 for the path exceptions.

@sponch This one: https://ca.cloudron.io/app/nextcloud-talk-hpb

@joseph aha, thanks! That is what I was looking for: [image: image.jpeg] And yeah @fbartels mine was still https://git.9wd.eu/apps/cloudron-cypht/raw/branch/main/CloudronVersions.json which is now a 404.

Packaged https://forum.cloudron.io/post/130303

The good news is that there are only two or three updates per year, so keeping the app up to date might require only a manageable amount of effort.

@Teiluj said: Thanks for considering packaging paperclip. We have created a package for Paperclip and have it running but are waiting to hear from upstream before publishing it.

Calibre-Web Automated suddenly gets an update after over 7 months! https://github.com/crocodilestick/Calibre-Web-Automated/releases/tag/v4.0.7

still all working well for me, but then i might not be touching all features important to everyone keep any feedback coming, want this to be the perfect setup for anyone wanting a private mesh network — which is very handy for offloading ai work to various other machines in your world, regardless of where you are exit-node feature is also handy, and nicely implemented — really impressed with their ease-of-use for clients if we can get cloudron to allow this as one of the vpn-protection options, i can see this being ideal for making cloudron corporate-friendly for anyone offering those kinds of services or wanting for yours and your family's locked-down access to apps

I did a quick research pass : viable defaults to full PyTorch which makes it a fat image, but could try the lite version with some compromises latest release is v0.10.5-alpha so still young as a repo and all recent releases are alpha None of those are blockers, just issues to deal with, might be a bumpy road until it is stable. I will add it to my 'Consider' list, maybe watch the repo a little, but if anyone else wants to get there first, please go ahead, don't let my looking at it dissuade any packagers.

@avatar1024 my AI analysis said possible but not easy. But my AI is normally cautious. Big question was whether it is single tenant or whether it should support accounting for multiple tenants. It's not something I am looking to take on currently (not just initial build but also maintenance).