Hi,

I have update the package to align to other jitsi-meet packages I maintain (stable, stable-bin, nightly, nightly-bin).

Now the package use Arch way for configs (/etc/jitsi-videobridge).

I made a blog post to configure jitsi-meet on arch. It use the -bin package, but now this one install files at the same places: https://blog.celogeek.com/posts/linux/archlinux/2020-06-jitsi-meet-on-arch-linux/

I'm working on alignment of all jitsi-meet packages. I will update the Arch Wiki as soon as I can.

Hi,

I have update the package to align to other jitsi-meet packages I maintain (stable, stable-bin, nightly, nightly-bin).

Now the package use Arch way for configs (/etc/jitsi-videobridge).

I made a blog post to configure jitsi-meet on arch. It use the -bin package, but now this one install files at the same places: https://blog.celogeek.com/posts/linux/archlinux/2020-06-jitsi-meet-on-arch-linux/

I'm working on alignment of all jitsi-meet packages. I will update the Arch Wiki as soon as I can.

Current config file has a typo: double-quote at the end of line 22 should be removed or the file won't get parsed correctly

I am not sure if this issue blocks you from running the JVB itself (my Jitsi instance is broken atm), but you can use jitsi-videobridge-git til a new release is tagged if it does.

Hi, can we follow more the debian upstream for this package?

• The install directory should be there: /usr/share/jitsi-videobridge.
• The service should be run as jvb:jitsi and not root!
• The service should start with hardened permission.
• You should have like the upstream those files in /etc/jitsi/videobridge: callstats-java-sdk.properties, config, log4j2.xml, sip-communicator.properties

I have made a standalone package here that does like the debian upstream:

https://github.com/celogeek/jitsi-meet-arch/blob/master/jitsi-videobridge/PKGBUILD

Hi,

Thanks for maintaining this package. Minor thing, but to follow same structure as the -bin equivalent, the path to the config file would be:

/etc/jitsi/videobridge/config

I updated the package to JVB2 - the config paths and format has changed.