Release v1.15.0 https://hub.docker.com/r/twentycrm/twenty/tags?name=v1.15.0 Quick update on the experience so far: REST and GraphQL APIs are well-documented, making it easy to integrate with other applications to complete business workflows. The CRM is simple, with core features that keep us focused and make daily operations easy, without being overwhelming with too many functions. Objects and fields are organized flexibly, allowing current business processes to be integrated smoothly. The interface is clean and visually pleasing, which makes it more motivating to use. Built-in automation workflows: easily run automated tasks without needing n8n or Make.

After a period of testing, I find Windmill truly excellent, and I really hope it will be available on Cloudron soon. This tool is powerful and stable.

@humptydumpty I have some notes that I put in QUICKSTART.md in /app/code. It's not a complete guide, just a quick start for basic config. But it does have some links to other proper guides. Storage : yep, I need to make a strategy. Currently my cameras back up via their NVR to a large Hetzner Storage Box. I am thinking to add some scripts to do similar, automatically moving ZM files off to Hetzner Storage Box based on time or size. And first step, find out what ZM provides to manage all this. Will update on my approach/experience as it builds.

@timconsidine nesting reverse proxies is OK. It happens already with Cloudron's Nginx and webservers that front multiple app servers in our Apps.

While planning another project which would benefit from Supabase, I used AI to take another look at viability of packaging Supabase. Answer : don't So nothing changed.

@zonzonzon said in Fizzy on Cloudron - the Kanban tracking tool for issues and ideas by 37signals: However, I think that at its current stage of development, the chance that the Cloudron team will package this app is extremely low. Why, given that @pathab has already packaged it?

I just started using Jmap because of ThunderMail (not Thunderbird), but I really like that server. @andreasdueren I think having an additional mail server app would be great, but the actual mail server is perfectly integrated into Cloudron itself. Nice find! If this server becomes more stable (see the breaking changes when updating: https://github.com/stalwartlabs/stalwart/blob/main/UPGRADING/v0_15.md), it could be a very nice drop-in replacement for the internal mail server as long as the licence (https://github.com/stalwartlabs/stalwart?tab=readme-ov-file#license) fits. However, reading the 'Enterprise' options (https://stalw.art/enterprise/), it may not be suitable because 'Multi-Tenant' is an 'Enterprise' feature. If I find some time, I can do some tests and post the results here, but that's low priority.

@sfeldkamp yeah, that works for the Cloudron package.

@humptydumpty / @loudlemur started working on AnythingLLM package, but (a) got diverted (b) wondered if needed because the native app is so good So it's parked for now.

Lets support XMPP on Cloudron by packaging Snickket! There is an ai summary of progress since @robi made the original request here: https://privatebin.demo.cloudron.io/?39e1a2ac0124f319#7wVtyc66t51BK2SpX7TudDPVpZm5sDqSmJCDvsrBqCXn

There is an ai summary comparing the relative merits of mostlymatter and rocket.chat here: https://privatebin.demo.cloudron.io/?4d4ec89bf8d15f94#2XdR8C2xbBzHRHZEfA2ZBSASHKhxokgsr79v31Xb6UtC

It seems that we are very nearly there with BTCpayserver. Lets wrap up this project and publish it officially on cloudron. Here are the main improvements on BTCserver just over the past year (2025): BTCPay Server Main Improvements (Jan 2025 - Jan 2026) POS & Checkout Tax rates applied to items with breakdowns in checkout/receipts Improved total breakdown, receipts, and cart views POS reports now include tips/subtotals Numeric keypad shows input amount (not total); item list support Receipts displayable in iframes; hide back-to-store link in iframes Disable zero-amount invoices; improved mobile UX Wallet & Transactions Wallet policy output descriptors (BIP388/389) and Taproot signing (BIP86) for hardware wallets RBF sweeping transactions and CPFP UX improvements Manual coin selection with advanced filters ("Clear All") Browse generated addresses; fiat amount previews in tx details Tx fee/fee rate info; exchange rate tracking; additional rates via store settings BBQr PSBT support (up to 16MB); improved PSBT error messages API & Greenfield New webhooks: InvoiceExpiredPaidPartial, InvoicePaidAfterExpiration amountPaid on invoices; email settings endpoint Subscriptions API; store users API (update/retrieve by ID/email) Payment requests link to external invoices (e.g., QuickBooks) via Reference ID PoS data without auth; payout methods optional for pull payments Histograms with Lightning data; image upload for app items Reporting & Invoices Renamed/reordered invoice report columns; export all metadata Payment request reports with improved filtering Refund reports; "Reporting" button for quick access Responsive UI; sales stats filter to paid invoices only Admin can view users' invoices; manual payout state transitions (InProgress → AwaitingPayment) Subscriptions & Automation Recurring payments with reminders; prefilled subscriber email Ambassadors can monetize server access Installable backend language packs Advanced server email rules (conditions, placeholders, CC/BCC) UI/UX & Accessibility Custom HTML meta tags/lang for SEO (crowdfund/PoS) Improved hardware wallet import (no confirm addresses page; auto-label by model) Dashboard tweaks (remove store headline, hide LN balance for non-admins) Tooltip/link for pull-payment tags; copy link button Auto-disable crashed plugins; cleanup expired data Integrations & Providers Phoenixd, Coinmate (CZK), Kraken (CAD), Yadio, Norwegian exchanges (Bitmynt/Bare Bitcoin) Fallback rate sources; rate providers configurable Shopify integration deprecation warning + new plugin link Multisig flow improvements (BTCPay-only users); confirmation prompts Bug Fixes & Reliability RBF label consistency; fee rate crashes; Yadio rate lookup Archived invoices private; status filter 500 errors Lightning payment detection post-connection string swap Vault signing for large PSBTs; pending payouts on unresponsive LN Notifications API crashes; Boltcard reset issues; escaped HTML in UTXOs Zero-amount payment requests; receipt options from store settings Sources: GitHub releases (up to v2.3.3), Changelog.md. Full notes: Releases.

ejabberd has had a lot of work to improve it since it was first requested by @jdaviescoates Lets support it on cloudron, now that we have version 9. ## ejabberd Main Improvements Since May 2020 ### Matrix Gateway (mod_matrix_gw) Enhancements - **Initial 1:1 support** (24.02+): Bridging to Matrix servers for direct messages. - **Room support** (25.03): Invitations to Matrix rooms, public room joins; MUC-like handling (versions 9-11 initially). - **Expanded room compatibility** (25.07/25.10): Older room versions, Hydra rooms (v12), state resolution rewrite, notary_servers/leave_timeout options. - **Other fixes**: No empty direct messages, double-colon JID for Hydra. ### Spam & Security Filtering - **mod_antispam** (25.07/25.10): Replaces mod_spam_filter; RTBL support for blocking spammer JIDs/URLs in messages/subscriptions. - **ACME fixes**: Erlang/OTP 28.0.2 compatibility. - **XEP-0425**: Moderated Message Retraction (24.12). ### New Modules & Discovery - **mod_providers** (25.10): Auto-generates/serves XMPP Providers JSON (XEP-0485) at /.well-known/xmpp-provider-v2.json. - **mod_pubsub_serverinfo** (25.07/25.10): PubSub Server Information for XMPP network graphs. - **mod_antispam**: Real-time block lists. ### XEP & Protocol Support - **XEP-0431**: Full Text Search in MAM (25.10?). - **XEP-0402**: PEP Native Bookmarks (24.12). - **XEP-0424**: Message Retraction (24.12). - **XEP-0369**: Latest MIX (23.01). - **MAM improvements**: archive_muc_as_mucsub option (25.10). ### Authentication & Config - **Multiple password types** (25.03): Simultaneous support. - **auth_password_types_hidden_in_scram1** (25.10). - **host_alias**, predefined keywords, rest_proxy options. - **ejabberdctl**: CTL_OVER_HTTP (25.03). ### API & Admin Tools - **New API Commands**: Inspired by XEP-0133 across modules (25.10). - **mod_configure**: access option (25.03). - **WebAdmin**: Link to Converse, formatting updates. ### Performance & Compatibility - **Erlang/OTP**: 25 required, 28 supported (25.10). - **SQL/MUC changes** (23.01+). - **Container images**: Macros, WebAdmin port exposure (25.03). ### Other Highlights - **Business Edition**: GCM/Webhook/Webpush fixes. - **General**: XEP-0313 MAM, HTTP Upload, vCard-temp; systemd integration, JWT auth, MQTT broker maturity (21.01+). Sources: GitHub releases (20.06–25.10), changelogs. Focus on user-impacting features; full details per release at https://github.com/processone/ejabberd/releases.

I started packaging Meilisearch I have a basic app packaged, but it is a bit hard-coded on indexing, so need to make it more flexible for different deployment and configuration scenarios, before sharing it.

My Hetzner Storage Box with SeaClone backup of test Cloudron-Seafile deployment [image: 1768223262316-screenshot-2026-01-12-at-13.07.14.png]

I'd love to have this. The current solutions, already existing on cloudron (@girish) are actually not that mature. I remember you saying, (for the former app-name, hoarder) it could be a hassle to publicize that, but I'd strongly disagree, as this app is simple, easy to use use and allows for a one-stop solution for many use-cases. Could you please take another look at it?

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.