Cloudron Forum

timconsidine

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)

timconsidine

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.

timconsidine

@humptydumpty
I will tidy it up (remove some debug code) and let you know when on CCAI.

timconsidine

@humptydumpty could be a good point

But I am NOT running on a GPU.
I just have a good Hetzner server (128Gb, good CPU).

I guess it's a limbo dance trial and error - how low can you go ?

I have a 'spare' testing Cloudron instance - very modest specs - just a mini PC - will give it a go over the weekend if I have a chance.

timconsidine

@Kubernetes ha ! I wish. My good friend TRAE helps me a lot, now with help of context7 and Sequential Thinking MCPs.

Amazing how stupid they can be at times, though !

Kubernetes

@timconsidine looks like you are 100% in a flow of productivity

timconsidine

@humptydumpty I am using Reolink cameras currently. Total of 12.

I need to play with resolutions.
The Reolink cameras and apps support 2k-4k.
For testing, I have only set the cameras up as 640x360, which explains why they are grainy in screenshots (and maybe why storage space is not increasing fast).

One motivation of getting Zoneminder working is freedom from the Reolink environment, and the ability to support more (cheaper/better) cameras without being tied to Reolink.

timconsidine

AnythingLLM is packaged !
A little bit of testing and clean-up needed,

Does anyone want it ?
Just depends whether I make repo public or private.

Cloudron team don't seem to want custom apps anymore <tease>

andreasdueren

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

andreasdueren

I packaged the Matrix Signal Bridge

Repo: https://git.due.ren/andreas/mautrix-signal-cloudron
Image: andreasdueren/mautrix-signal:1.0.2

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

Cloudron Forum

AppDev

Posts

Member List