Matrix/Riot
-
@girish My concern is having anything at example.com
It would be cleaner to just have cloudron handle that for me. Small gripe, not a big deal at all. -
@will said in Matrix/Riot:
It would be cleaner to just have cloudron handle that for me. Small gripe, not a big deal at all.
Ah, Cloudron side limitation can definitely be fixed
I agree that having to ssh and put files manually in a cryptic location is kinda crude. This will be fixed soonish but we just wanted to get the apps out for testing sooner rather than later.
-
@girish Dont get me wrong, Im thankful! Its great. I'm just giving a little feedback on possible improvements. Sounds like you are on it already
-
@msbt said in Matrix/Riot:
I'm guessing it is because of new keys and everything, haven't tried to re-use any of the existing ones.
Might very well be, yes. I'm going to try and migrate the keys too. The migration is hard to dry run though
-
if you want to make sure this works, you could try with a test-instance, after that a clone and then the real thing
good luck either way!
-
I'm transitioning my external reverse-proxy-and-well-known solution to the Cloudron solution. Is there any way I can configure Riot to have
https://domain.tld
asbase_url
while still having the Synapse server athttps://matrix.domain.tld
? This way I would be able keep Riot user sessions across migration. -
@yusf That should not be a problem. Riot can be installed on the main domain as well. Just make sure the
.well-known
is setup on the server. -
@girish Sorry, I meant doing so while keeping Riot at a subdomain too. I guess not?
-
@yusf Yeah, I think not
-
FWIW, I just installed all of this and tested it. Works great, instructions are clear. The yaml edits referenced by @msbt were quite helpful on the external-registration side.
Look forward to the eventual Jitsi package.
-
@girish What if I edited the Cloudron reverse proxy settings directly?
-
@yusf reverse proxy configs will get overwritten during updates. I think https://cloudron.io/documentation/apps/#well-known-uris should help setup well knowns the way you want them, no?
-
@girish Well-known is in place for Synapse already, but it seems that well-known configurations aren't enough to enable entering
domain.tld
as homeserver in Riot sign-in when the server is atmatrix.domain.tld
.What seems to be needed is the ability to forward the whole
/_matrix
path atdomain.tld
to Synapse.In nginx terms I belive that would look something like this:
server { listen 443; server_name domain.tld; location /_matrix { proxy_pass https://matrix.domain.tld; } }