Selfhosted

39903 readers

463 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

jitsi .. redundant setup ? (infosec.pub)

submitted 10 months ago by kristoff@infosec.pub to c/selfhosted@lemmy.world

2 comments fedilink hide all child comments

H all, Somebody here selfhosting jitsi meet?

I am working on a jitsi-meet setup for an organisation, now looking at the options for redundancy.

I have noticed you can configure multiple XMPP servers on the jitsiivideobridge. What is the exact goal of this?

Can you connect a jvb to multiple jitsj servers (domains)? or is this only for making the jitsii backend redundant?

Kr.

you are viewing a single comment's thread
view the rest of the comments

[–] poVoq@slrpnk.net 2 points 10 months ago (1 children)

A lot of the stuff in Jitsi meet is a result of their internal setup and it isn't imediatly clear how it would be useful to other infrastructure.

I guess it might be related to some compartmentalization of customer deployments while sharing a high performance video bridge cluster or so.

I think the better question is to ask what you actually need rather than what obscure featured jitsi might have.

[–] kristoff@infosec.pub 2 points 10 months ago

For me, the first goal is to simply understand the setup. I now have been able to create a setup with two frontend jvb-instances and one backend. In the end, the architecture setup of a jitsi-server is quite nicely explained, and -by delving a little bit into the startup scripts of the docker-based jitsi setup, you do get some idea of how things fit together.

From a practicle point of view, I think I'll go for the basic setup (1 backend, 2 frontends) natively on two servers, and -if the backend server would go down- just have a dockerised backup-setup ready to go if it would be needed.

Thanks!