From: flupe <flupe@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: soju-0.2.1
Date: Mon, 04 Oct 2021 20:49:30 +0200 [thread overview]
Message-ID: <20211004184930.yslziWsInd5lr9vxrp2Coa30VkuF8et8taSITdqQt0A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33302@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
New comment by flupe on void-packages repository
https://github.com/void-linux/void-packages/pull/33302#issuecomment-933731857
Comment:
@Duncaen
> This should use a separate user, there is no reason to run an irc bouncer as root.
I completely agree with this statement. My only gripe was that the database is only created when running `sojuctl`:
```
sojuctl -config /etc/soju/config create-user username -admin
```
And users would have to make sure it is ran as `_soju` so that the service can read it. Is there a way to document this?
~~Also, is there a naming convention for system users on void, why `_soju` rather than `soju`?~~ (Ah, found it on the manual)
> I also switched the log and database directories, not sure if this would make sense:
Yes, makes a lot of sense. On it.
next prev parent reply other threads:[~2021-10-04 18:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 21:43 [PR PATCH] " flupe
2021-10-03 22:52 ` Vaelatern
2021-10-04 8:12 ` [PR PATCH] [Updated] " flupe
2021-10-04 8:14 ` flupe
2021-10-04 11:14 ` [PR REVIEW] " flupe
2021-10-04 11:24 ` paper42
2021-10-04 11:27 ` paper42
2021-10-04 12:41 ` [PR PATCH] [Updated] " flupe
2021-10-04 12:47 ` flupe
2021-10-04 16:31 ` Duncaen
2021-10-04 16:32 ` Duncaen
2021-10-04 18:13 ` flupe
2021-10-04 18:49 ` flupe [this message]
2021-10-04 19:28 ` [PR PATCH] [Updated] " flupe
2021-10-04 19:30 ` flupe
2021-10-04 19:39 ` Duncaen
2021-10-04 21:25 ` [PR PATCH] [Updated] " flupe
2021-10-04 21:26 ` flupe
2021-10-04 21:50 ` [PR REVIEW] " Duncaen
2021-10-04 22:52 ` flupe
2021-10-04 22:58 ` [PR PATCH] [Updated] " flupe
2021-10-04 23:33 ` [PR REVIEW] " Duncaen
2021-10-04 23:35 ` Duncaen
2021-10-04 23:35 ` Duncaen
2021-10-05 10:26 ` [PR PATCH] [Updated] " flupe
2021-11-20 22:57 ` Duncaen
2021-11-20 22:58 ` Duncaen
2021-11-21 8:42 ` [PR PATCH] [Updated] " flupe
2021-11-21 8:48 ` flupe
2021-11-21 8:53 ` New package: soju-0.3.0 flupe
2021-11-21 17:35 ` [PR PATCH] [Merged]: " Vaelatern
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=20211004184930.yslziWsInd5lr9vxrp2Coa30VkuF8et8taSITdqQt0A@z \
--to=flupe@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).