4 Jun 2021 |
Dalek | ah, yes.... RTFM n'est pas ? 😀 Thank you | 16:13:57 |
Dalek | natrius: I'm guessing you're the author, am i right? | 16:16:37 |
Stefan | :D | 16:17:43 |
Stefan | Yupp | 16:17:50 |
Dalek | I promise to feed back.... i like your Wiki theme.... best i've ever seen.... That's MediaWiki ? | 16:20:05 |
Stefan | DokuWiki | 16:20:44 |
Dalek | 👍️ looks good | 16:21:05 |
Dalek | i run 'ss -plntu' and get a lot of output, because i already have quite a lot of stuff running on my server.... it would be cool to provide a command filtered through grep (for instance) so that i only see out output that actually interest me in this case, about Matrix Synapse..... (HTH with the comments, it's intended to be constructive feedback not carping...... i'm a professional tech documentation writer if you want some contributed collaboration on this) | 16:27:28 |
Stefan | Just blurt out with your ciritque and don't hold back. :) | 16:28:20 |
Stefan | No need to apoligize and whatever. | 16:28:33 |
Dalek | ;-) ok .................... netstat -lnpt gives more-readable output | 16:29:06 |
Dalek | and even that could be grep'ed just to return the relevant info | 16:29:38 |
Dalek | "Synapse is now up and running using the default configuration on port '8008' and '8448'. Check the open ports using ss (former netstat) command."
At the end of step 2, I only have Synapse running on 127.0.0.1:8008 .............. nothing at all on 8448 as yet.......... | 16:33:17 |
Stefan | netstat is old, thats why its ss now | 16:33:35 |
Stefan | deprecated (forgot the word :D ) | 16:33:47 |
Stefan | Uh, you are correct, 8448 is now gone as well. | 16:34:30 |
Stefan | What do you use for your work on docs? latex? Out of curiosity. | 16:34:47 |
Dalek | well, i usually just use Word from Office 365...... or Trados if i'm translating documentation (my core profession is technical translation) | 16:36:22 |
Dalek | maybe netstat is "deprecated" ;-) but ss is returning so much verbose output it's mind-blowing for a newbie :-D | 16:38:29 |
Stefan | I'm sure we can work on that :) | 16:41:48 |
Dalek | I gave it all a quick read through before i actually start my installation...
In reality, I already have Synaps installed but broken, so I need to follow your guide and make sure my installation is 'aligned' on it as regards the important points....
I think i could indeed make some helpful contributions here.....
For a start. "After the Synapse installation, we will configure it to run under the local IP address" ......... Well, in reality, most people don't have any use for running Synapse as a local instance...... What they want to do, is to put it on the Web, on a real IP address,.
In my own case, I have it on a server that has half a dozen IP addresses, so the 'default server' configuration of Nginx does not help me..... I need the configuration tailored for one particular IP address | 16:49:33 |
Dalek | Also, reading the guide, one of my main confusions is not addressed: I have my Synapse running on an IP address (exposing Synapse on dalek.zone) ........ But I also have Element running on the same IP address but a DIFFERENT DOMAIN...... matrix.dalek.zone ........... so i find homeserver.yaml to be very confusing as regards where it refers to the actual Matrix Synaps and where it refers to the client Element............... | 16:52:53 |
Stefan | Basically everything is exclusively synapse. | 16:53:51 |
Stefan | No clue how you get that anything has to do with element. | 16:54:15 |
Stefan | I mention in the last step "now login in the client" as far as i remember :D | 16:54:36 |
Stefan | To the ip-problem, i get what you mean, i think | 16:55:37 |
Stefan | give me a sec | 16:56:16 |
Stefan | The point of my guide is to get up and running on your own server as fast as possible without to much explanation. | 16:56:56 |
Stefan | If someone has a server with a lot of ip adresses and a nginx running my conclusion is: not a newb, should get up a custom nginx for an URL | 16:57:25 |
Stefan | But i will think about it. | 16:57:53 |