Yeah but that would be totally new

Not at all new, just unexplored.

It's a trivial config change with zero impact on Cloudron and additional DinD benefits.

@micmc said in Jitsi - Package Updates:
I wouldn't discount that. Or use the virtualized word as it is merely containerized.

This means Docker in Docker (DinD) functionality, which can be done on Cloudron if you switch to using the newer docker runtime called Sysbox from Nestybox, which Docker recently acquired.

Yeah but that would be totally new, and not a bad news at all as a matter of fact, as until now DinD with Cloudron was to be kept out of bound, as far as I knew. But hey things change every hour in this world

We have threads on this in the forum.

Will check it out for sure, but then, thinking about that, if it might work but that would require much resources?

Nah, too bad you cannot count on eventually running OpenTalk on Cloudron either because as I reported here it is already meant, built and working with full virtualization (reminds much of how Cloudron is conceived).

So that would means running a virtualized environment on, or within a virtualized environment... and that is absolutely NOT recommended in the case of Cloudron.

I wouldn't discount that. Or use the virtualized word as it is merely containerized. This means Docker in Docker (DinD) functionality, which can be done on Cloudron if you switch to using the newer docker runtime called Sysbox from Nestybox, which Docker recently acquired.

We have threads on this in the forum.

@avatar1024 said in Jitsi - Package Updates:

Indeed! Jitsi seems like it's gone sour a bit.

OpenTalk architecture doesn't feel any easier (https://gitlab.opencode.de/opentalk), nor OpenTalk provides mobile app.

I ended up running Jitsi on a bare (virtual) server - it works quite well, you just have to consider the whole Linux server as your Docker and avoid touching it as much as you can.

Nah, too bad you cannot count on eventually running OpenTalk on Cloudron either because as I reported here it is already meant, built and working with full virtualization (reminds much of how Cloudron is conceived).

So that would means running a virtualized environment on, or within a virtualized environment... and that is absolutely NOT recommended in the case of Cloudron.

As far as thing goes right now, I think it's a good choice to run Jitsi on its own dedicated rig if it's worth it, meaning mettings with more than 4-6 I'd say.

Now, I've yet to dig deeper but it seems that our best real alternative until now would be MiroTalk.

Indeed! Jitsi seems like it's gone sour a bit.

OpenTalk architecture doesn't feel any easier (https://gitlab.opencode.de/opentalk), nor OpenTalk provides mobile app.

I ended up running Jitsi on a bare (virtual) server - it works quite well, you just have to consider the whole Linux server as your Docker and avoid touching it as much as you can.

Though opentalk looks more feature rich for sure!

Yeah, once I read https://opentalk.eu/en/product/features I really wanted it! It sounds fantastic!

Though opentalk looks more feature rich for sure!

Unfortunately after a few lengthy attempts to update the app, we failed so far.

Thanks the efforts.

I've never actually tried it, but per eg this post perhaps time would be better spent trying to package OpenTalk