🧪 Testers wanted: Element Server Suite (ESS Community) for Cloudron
-
@andreasdueren Hi Andreas. Why does v0.3.32 require a manual update?
@humpty v0.3.32 moved the package image from Docker Hub to the new Cloudron Container Registry as part of the Cloudron 10 build-system migration. Cloudron intentionally requires manual confirmation whenever a community package changes its image repository, as a security precaution. This should be a one-time manual update; later versions from the new repository will update automatically again.
-
I'm really interested in switching over from Synapse-only to this.
As of now just so I'm sure, this is still waiting on some work from @girish, @james and the cloudron team in order for instances that are on 'matrix.mydomain.com' (for example) to work correctly, right?
-
I'm really interested in switching over from Synapse-only to this.
As of now just so I'm sure, this is still waiting on some work from @girish, @james and the cloudron team in order for instances that are on 'matrix.mydomain.com' (for example) to work correctly, right?
@DidierMalenfant The Package works as is without limitations except for it blocking the apex domain.
-
@DidierMalenfant The Package works as is without limitations except for it blocking the apex domain.
@andreasdueren meaning you can't have an app installed on the apex domain, right?
-
@andreasdueren meaning you can't have an app installed on the apex domain, right?
@DidierMalenfant correct. Pending an update to Cloudron to not make this necessary anymore.
-
@andreasdueren Gotcha. I have Mastodon on my apex domain so I need to wait
@girish you mentioned this could be looked at after 10.x ships?
-
-
@girish It was about this feature request. And while you're at it, please also deploy this one, it's messing with my workflow
-
-
@didiermalenfant yup, I took a quick look at the state of matrix again. ESS is more like a full stack deployment. It is not in our plans to provide this package since I think it's very complicated to maintain. Our current approach is to provide these as separate packages. Upstream also pushes releases of all these parts separately, so the update cadence makes sense for us.
- I looked into if we need to add some additional well-known configs. It looks like we are up to speed here . See my note in https://forum.cloudron.io/topic/15818/define-custom-well-known-entries-via-cloudronmanifest.json
- We need to integrate MAS into our existing Synapse package. For this, we need multiple database support in postgresql addon. I have added this now in 10.2
- Once 10.2 is out, we will release a major upgrade of Synapse that will migrate to this new MAS+Synapse. With that Element X will work.
- AFAICT, https://github.com/element-hq/element-admin/ is a pure static page. But we can get this published as an app separately or integrate this into existing synapse package. I have create a work item internally.
Hope that helps.
-
Thanks @girish I really appreciate the feedback and look forward to the upcoming MAS and Synapse packages.
The part of ESS I'm most interested in is Element Call. Do you plans include getting this working too?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login