Hacker News Reader

Comment by fiatjaf | Hacker News Reader

I tried to run a Jitsi server. It's a madness full of Docker impossible things to run and a very long and confusing configuration file.

I wonder why can't these things be provided as binaries with a simple set of settings.

Now they offer Jitsi as a service for free up to 25 users? That's great though. It should cover 99% of normal people use cases, so no one will use meet.jit.si anymore.

View on HN

Over at The Document Foundation, we use a Salt setup with no Docker: https://git.libreoffice.org/infra/salt/+/refs/heads/master/j...

> I tried to run a Jitsi server. It's a madness full of Docker impossible things to run and a very long and confusing configuration file.

Sorry to hear that. Any chance you can provide some more details on what you tried and didn't work? I'd like to improve on this.

> I wonder why can't these things be provided as binaries with a simple set of settings.

That's kind of what they already are, but at certain degree of complexity it unfortunately leaks back to the user.

No, sorry, I don't remember anymore. But it was just a hobby server for a group of friends to use and we've given up since.

I just remember being forced to install docker and edit a docker-compose.yml, and then configs would show up in other parts of the system that were not the directory I was in.

Then finally I got the server and people could join but they couldn't see the others. Anyway, I probably didn't invest the right amount of time and focus to get it working.

I set up a Jitsi instance last year, and it didn't involve Docker at all. Getting the ports set up was the biggest issue.

I used this guide: https://jitsi.github.io/handbook/docs/devops-guide/devops-gu...

I don't know about others but I much prefer running a docker container than a random binary.

Reply on news.ycombinator.com