Github messages for voidlinux
 help / color / mirror / Atom feed
From: freshprince <freshprince@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: synapse: minor changes.
Date: Mon, 03 Jan 2022 09:55:10 +0100	[thread overview]
Message-ID: <20220103085510.p--9pJXma-UFFmcmqZl5WDc17lt87vazb4KxfPr-wzU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34676@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1704 bytes --]

New comment by freshprince on void-packages repository

https://github.com/void-linux/void-packages/pull/34676#issuecomment-1003946637

Comment:
> Being able to see those configuration problems raised in syslog makes debugging easier.

Syslog is not installed by default on void so you won't see the problems raised anywhere. If you think that installing socklog-void and knowing where vlogger logs to by default is easier than using `ps` and `pgrep runsvdir | xargs -I{} cat /proc/{}/cmdline` you should consider reading up on [runit](http://smarden.org/runit/). Which is the init system that void is using. 

> The Debian package maintained by the authors does the same thing

That's a nice form of cargo-cult that begs for the statement that if you like how it's done in distribution X maybe you should switch to distribution X. If I remember correctly void is trying to provide packages as 'vanilla' as possible.

If one seriously wants to set up a synapse homeserver, they have to install synapse, get valid ssl certificates, set up a reverse proxy, install postgresql and set it up, add well-known files for clients and federation, have a working e-mail setup, set up a TURN server and start running different worker processes to do load balancing. I don't think that copying sample config files so that the service starts without failing after a fresh install helps a beginner doing any of that. But it might have wrong defaults like the name of the homeserver (which makes the generated sqlite-db unusable if you want to switch the name later) and missing randomly generated secrets as already mentioned. It also introduced problems for people that were already having a working setup.


  parent reply	other threads:[~2022-01-03  8:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23  7:53 [PR PATCH] synapse: update to 1.49.2 freshprince
2021-12-23  8:01 ` [PR PATCH] [Updated] " freshprince
2021-12-30  2:57 ` TinfoilSubmarine
2021-12-30  2:59 ` TinfoilSubmarine
2021-12-30  3:11 ` TinfoilSubmarine
2021-12-30 10:44 ` freshprince
2021-12-30 10:54 ` freshprince
2021-12-30 14:49 ` TinfoilSubmarine
2021-12-31  8:51 ` [PR PATCH] [Updated] " freshprince
2021-12-31  8:53 ` freshprince
2021-12-31  9:02 ` freshprince
2021-12-31  9:11 ` [PR PATCH] [Updated] synapse: minor changes freshprince
2021-12-31 17:09 ` TinfoilSubmarine
2022-01-03  8:55 ` freshprince [this message]
2022-01-03 16:03 ` TinfoilSubmarine
2022-01-03 16:20 ` freshprince
2022-01-03 17:44 ` TinfoilSubmarine
2022-01-03 17:44 ` TinfoilSubmarine
2022-01-05  0:58 ` TinfoilSubmarine
2022-01-05  8:20 ` [PR PATCH] [Updated] " freshprince
2022-01-05 12:18 ` freshprince
2022-01-19 10:45 ` freshprince
2022-01-19 10:45 ` [PR PATCH] [Closed]: " freshprince

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220103085510.p--9pJXma-UFFmcmqZl5WDc17lt87vazb4KxfPr-wzU@z \
    --to=freshprince@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).