Cloudron Forum

I am using self-hosted Netbird (deployed on a VPS) It works great !! "unifies" devices across different networks and locations Personally I find it easier than Cloudron VPN, but maybe I should review the Cloudron offering again

@robi I have been exploring that extensively, but so far no joy. I am persevering ....

I just noticed TODAY that my VW was down. Thanks @james @christophermag for the fix. I also ran into the windows 11 copy/paste issue. [image: 1768691336467-yousavedthedaygif.gif]

OMG an integration Ok will investigate

@canadaduane I think @andreasdueren has packed WhatsApp and Signal bridges for Matrix

@girish would this be more applicable to the planned VPN work which can expose hidden/private/temp/test services through an useful subdomain tied to an IP:port configuration?

@drm237 said in Windmill: Open-source alternative to Airplane, Superblocks, Retool: I submitted a pull request if anyone wants to give it a try: https://github.com/halecraft/windmill-cloudron/pull/1. It assumes that @canadaduane didn't update the init-db-as-superuser.sql file in their original build and instead fetches the original file from windmill. Merged! And I'm sorry it took so long to see it. I must have cleared out my github inbox without noticing.

@sangemaru said in MCP Server for Cloudron - AI-Powered Instance Management: Would be great if you can make your fork repo public. Done! https://github.com/halecraft/mcp-cloudron @sangemaru said in MCP Server for Cloudron - AI-Powered Instance Management: And, I hope you'll excuse the pun, but you could totally rock "The Rock" Johnson as a nickname. Ha! I have been told my nickname should be The Pebble (if you compare, you would see why :D) Have a great day, Duane

The performance depends on the model you load and run. One guy found out he could run a small model (gemma 3) on his CPUs as multiple agents which fronts other API based models and agents who do heavier lifting.

Update January 2026 My packaging of Parse Server and Parse Dashboard was a bit "hacky". So I decided to start again. I have deleted the old repos on git.cloudron.io as I am not clear about their robustness. I am much happier with the new one. This packages Parse Server and Parse Dashboard as one Cloudron app so users can get an 'out of the box' deployment. If there is demand, I can make alt versions which deploy the Server and Dashboard separately, so for power users they can have 1 x Dashboard and 5? x Server apps. Also, @jdaviescoates mentioned a preference for Postgres backend. If there is demand for that, I can produce an alt version with Postgres instead of MongoDB. NEW REPO : https://git.cloudron.io/timconsidine/cloudron-parsesuite Will get round to releasing it on Custom App Installer (ccai.appx.uk)

So from a packager’s perspective, it’s been very workable and maintainable. Well done ! @pathab said in Fizzy on Cloudron - the Kanban tracking tool for issues and ideas by 37signals: If anyone wants to try it out themselves, the user will also need the relevant CloudronManifest.json as well, and maybe any files it references (e.g. POSTINSTALL.md). I can add it to my custom app installer a bit later, unless you prefer me not to do so.

I'm using an Amcrest 5MP POE Dome at work with BlueIris at one level behind whatever the max resolution is (higher frame rate). The second cam I bought that I'll be using to test ZM is a REOLINK E1 Pro 3K PT Wi-Fi. Both are 5MP around 2K res iirc. Yeah, the Amcrest motion recordings are in the +1GB range for me. I have BI save to a local nextcloud folder which then gets synced to the server. I also have it taking screenshots and emailing two different resolutions for a quick lookup. Looking forward to testing ZM soon as I forego the local backup addition for now.

Title: TastyIgniter on Cloudron - Open Source Restaurant Management System Main Page: https://www.tastyigniter.com Git: https://github.com/tastyigniter/TastyIgniter Licence: MIT Dockerfile: Yes Demo: https://tastyigniter.com/demo Summary: TastyIgniter is a free and open-source restaurant ordering and management system built on the Laravel PHP framework. It provides a complete solution for restaurants to manage online orders, reservations, menus, staff, customers, and reports. The platform includes features for multi-location support, table management, delivery tracking, payment processing, and a customer-facing ordering system. Notes: TastyIgniter is an excellent choice for restaurants looking for a self-hosted alternative to commercial POS systems. The application is actively maintained, has a strong community, and offers both free core features and premium marketplace extensions. TastyIgniter handles multi-location restaurant chains well and provides comprehensive reporting and analytics features. Alternative to / Libhunt link: GloriaFood, TouchBistro, Toast POS and Lightspeed Restaurant Screenshots: [image: storefront.png] [image: Menus.png] [image: admin-dashboard.png]

Hello @mononym I think I see the issue in the app and will try to reproduce the issue and find a solution.

I did some digging, this is what I think is needed: The current package uses: Synapse v1.144.0 (which is compatible - MAS requires v1.136.0+) Cloudron OIDC for SSO (traditional OIDC provider approach) PostgreSQL as the database Standard Matrix authentication endpoints What MAS Integration Requires MAS is fundamentally different from traditional OIDC - it's not just another identity provider, but a complete replacement for Synapse's internal authentication system per MSC3861. It needs: 1. MAS Service Deployment MAS needs to run as a separate service (not just a config change) It requires its own separate PostgreSQL database It needs its own domain/subdomain (e.g., auth.matrix.example.com) Docker image: ghcr.io/element-hq/matrix-authentication-service:latest 2. MAS Configuration Requirements Encryption secrets and signing keys (RSA minimum) Connection to Synapse via shared secret Database configuration for its own PostgreSQL database HTTP listener configuration Email configuration for password recovery Policy configuration (WASM file) 3. Synapse Configuration Changes Replace traditional OIDC with matrix_authentication_service section: matrix_authentication_service: enabled: true endpoint: http://mas-internal:8080/ secret: "SharedSecretWithMAS" 4. Reverse Proxy Changes These Matrix endpoints must be routed to MAS (not Synapse): /_matrix/client/*/login /_matrix/client/*/logout /_matrix/client/*/refresh 5. User Migration (For Existing Deployments) MAS includes syn2mas tool to migrate: Existing password hashes (bcrypt → argon2id) Sessions and devices Access tokens Upstream IdP mappings