Jitsi Meet: Difference between revisions

From Alpine Linux
(→‎Videobridge: package is in testing)
(Delete obsolete NOTE)
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Obsolete|Jitsi seems to be available in the testing repository}}
{{Obsolete|Jitsi seems to be available in the testing repository}}
NOTE: this will build the applications required for a jitsi-meet server on Alpine Linux. Prosody (apk) plus videobridge and jicofo using latest 'stable' on jitsi GH repo.
Tested on 'edge', should work on 3.12 (not tested)


NOTE TODO: I will return and update this page with config files and rc scripts. But it's similar to the Debian config.  Also TODO nginx reverse proxy / bosh config.  
NOTE TODO: I will return and update this page with config files and rc scripts. But it's similar to the Debian config.  Also TODO nginx reverse proxy / bosh config.  
Line 60: Line 57:
<pre>
<pre>
# prosodyctl restart
# prosodyctl restart
</pre>
== Java/Maven setup ==
Maven is used to build videobridge and jicofo. Shell scripts included in software use bash. Jitsi uses jdk8, so should probably stick with that version. If you get fancy and use a newer jdk it might not work.
<pre>
# apk add openjdk8
# apk add maven
# apk add bash
# apk add bash-completion
# sync
</pre>
</pre>


Line 78: Line 62:
== Videobridge ==
== Videobridge ==


The <code>jitsi-videobridge</code> package is available in the <code>edge</code> repositories. For a stable release of Alpine, it needs to be built manually.
The <code>jitsi-videobridge</code> package is available in the <code>testing</code> repositories. For a stable release of Alpine, it needs to be built manually.


== Jicofo ==
== Jicofo ==


The download archive file from GH is the same name as videobridge, so we can put the new build in a separate directory.
The <code>jicofo</code> package is available in the <code>testing</code> repositories. For a stable release of Alpine, the aport needs to be built manually.
 
<pre>
# mkdir jicofo
# cd jicofo
# wget https://github.com/jitsi/jicofo/archive/stable/jitsi-meet_4627.tar.gz
# tar xf
# cd jicofo-stable-jitsi-meet_4627
# mvn -DskipTests -Dassembly.skipAssembly=false package
</pre>
 
You should get output like this:
 
<pre>
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  42.191 s
[INFO] Finished at: 2020-07-14T04:07:40Z
[INFO] ------------------------------------------------------------------------
</pre>
 
<pre>
# cd target
# unzip jicofo-1.1-SNAPSHOT-archive.zip
</pre>


== Jigasi ==
== Jigasi ==


Note: Optional. Jigasi is a SIP to Jitsi-Meet interface/gateway. This can be used to allow SIP and POTS users to "call in" to a meeting.
The <code>jigasi</code> package is available in the <code>testing</code> repositories. For a stable release of Alpine, the aport needs to be built manually.
 
<pre>
# wget https://github.com/jitsi/jigasi/archive/master.zip
# unzip master.zip
# cd jigasi-master
# mvn -DskipTests -Dassembly.skipAssembly=false package
</pre>
 
You should receive a similar message:
 
<pre>
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:50 min
[INFO] Finished at: 2020-07-14T17:14:12Z
[INFO] ------------------------------------------------------------------------
</pre>
 
<pre>
# cd target
# unzip jigasi-linux-x64-1.1-SNAPSHOT.zip
</pre>

Latest revision as of 09:21, 7 July 2024

This material is obsolete ...

Jitsi seems to be available in the testing repository (Discuss)

NOTE TODO: I will return and update this page with config files and rc scripts. But it's similar to the Debian config. Also TODO nginx reverse proxy / bosh config.

Prosody

# apk add prosody

edit /etc/prosody/prosody.cfg.lua

generate certs: Edit /etc/prosody/certs/openssl.cnf

[FQDN] means www.example.com 

# cd /etc/prosody/certs
# make [FQDN].cnf

edit file and make sure everything is correct 

# make [FQDN].key

for self-signed certificate: 

# make [FQDN].crt

or, for signing request: 

# make [FQDN].csr

NOTE: repeat cert process for: auth.[FQDN] (ie, auth.www.example.com)

If you self-signed the cert, put it in the certs folder so it will be trusted on the local machine. 

# ln -sf /etc/prosody/certs/auth.[FQDN] /usr/local/share/ca-certificates/
# update-ca-certificates -f

# prosodyctl start

# prosodyctl register focus auth.[FQDN] YOURSECRET3

(YOURSECRET3 is from cfg file /etc/prosody/prosody.cfg.lua) 

# prosodyctl restart


Videobridge

The jitsi-videobridge package is available in the testing repositories. For a stable release of Alpine, it needs to be built manually.

Jicofo

The jicofo package is available in the testing repositories. For a stable release of Alpine, the aport needs to be built manually.

Jigasi

The jigasi package is available in the testing repositories. For a stable release of Alpine, the aport needs to be built manually.

Retrieved from "https://wiki.alpinelinux.org/w/index.php?title=Jitsi_Meet&oldid=26916"