This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
computing:synapse [2022/11/24 03:52] – oemb1905 | computing:synapse [2022/12/11 21:48] – oemb1905 | ||
---|---|---|---|
Line 3: | Line 3: | ||
* **Jonathan Haack** | * **Jonathan Haack** | ||
* **Haack' | * **Haack' | ||
- | * **webmaster@haacksnetworking.org** | + | * **webmaster@haacksnetworking.org** |
------------------------------------------- | ------------------------------------------- | ||
Line 146: | Line 146: | ||
< | < | ||
- | 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 176: | Line 189: | ||
- VM Backup Script: [[https:// | - VM Backup Script: [[https:// | ||
- | Lastly, I also have a hot-spare in case my co-located hardware fails. | + | Lastly, I also have a hot-spare in case my co-located hardware fails. |
+ | |||
+ | - [[https:// | ||
- | --- // | + | --- // |