This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
computing:synapse [2022/11/23 07:21] – oemb1905 | computing:synapse [2024/01/30 03:17] (current) – oemb1905 | ||
---|---|---|---|
Line 3: | Line 3: | ||
* **Jonathan Haack** | * **Jonathan Haack** | ||
* **Haack' | * **Haack' | ||
- | * **webmaster@haacksnetworking.org** | + | * **webmaster@haacksnetworking.org** |
------------------------------------------- | ------------------------------------------- | ||
Line 84: | Line 84: | ||
sudo --user elementweb tar -xvf element-v1.10.12.tar.gz | sudo --user elementweb tar -xvf element-v1.10.12.tar.gz | ||
rm element-v1.10.12.tar.gz | rm element-v1.10.12.tar.gz | ||
- | cd /var/www/elemenet.gnulinux.club/ | + | cd /var/www/element.gnulinux.club/ |
ln -s element-v1.10.12/ | ln -s element-v1.10.12/ | ||
- | cd /var/www/elemenet.gnulinux.club/ | + | cd /var/www/element.gnulinux.club/ |
- | cp config-sample.json config.jason | + | cp config-sample.json config.json |
nano config.json | nano config.json | ||
<" | <" | ||
Line 142: | Line 142: | ||
< | < | ||
< | < | ||
- | < | + | < |
< | < | ||
< | < | ||
- | Again, note that there is no need to set up an incoming email server nor tolerate spam on the server you are sending to. In my case, my smtp server / MTA is a relay with domains that are allowed to send through it explicitly white listed. Alright, so now it's time to carry on with setting up jitsi. Again, as with element and matrix, always check the [[https:// | + | Again, note that there is no need to set up an incoming email server nor tolerate spam on the server you are sending to. In my case, my smtp server / MTA is a relay/MTA (only) |
+ | |||
+ | sudo nano / | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | |||
+ | Also, make sure to add the following line of code within each nginx http server block: | ||
+ | |||
+ | < | ||
+ | |||
+ | Alright, so now it's time to carry on with setting up jitsi. Again, as with element and matrix, always check the [[https:// | ||
curl https:// | curl https:// | ||
Line 165: | Line 178: | ||
systemctl restart matrix-synapse | systemctl restart matrix-synapse | ||
| | ||
- | You can verify that jitsi is working by '' | + | You can verify that jitsi is working by '' |
+ | |||
+ | https:// | ||
+ | wget https:// | ||
+ | tar -xvf element-v1.11.55.tar.gz | ||
+ | cd / | ||
+ | cp -ar config.json ../ | ||
+ | ln -s element-v1.10.12/ | ||
+ | |||
+ | Make sure to have .well-knowns established for client and support | ||
+ | |||
+ | sudo touch / | ||
+ | |||
+ | With the following: | ||
+ | |||
+ | { | ||
+ | " | ||
+ | " | ||
+ | } | ||
+ | } | ||
+ | |||
+ | Also identify support: | ||
+ | |||
+ | sudo touch / | ||
+ | |||
+ | With the following: | ||
+ | |||
+ | {" | ||
+ | |||
+ | Finally, make sure that browsers don't download these by adding | ||
- | [[https://repo.haacksnetworking.org/ | + | location |
+ | allow all; | ||
+ | add_header access-control-allow-origin *; | ||
+ | add_header content-type application/ | ||
+ | } | ||
- | Utilize rsync or similar to ensure you have those backups offsite as well as on site, and also provision a hot-spare in case your self-hosted or co-located hardware fails. | + | More updates below when they come. |
- | --- // | + | --- // |