diff options
| author | V <v@unfathomable.blue> | 2021-08-17 03:14:25 +0200 |
|---|---|---|
| committer | V <v@unfathomable.blue> | 2021-08-17 05:01:25 +0200 |
| commit | 1c9978010c2616ec664d9febc14beb1625f5f903 (patch) | |
| tree | 1145249aa2d6e681913223a8953c935d1956a885 /fleet/pkgs/group-readable-archives.patch | |
| parent | ec0965e2672899d25a5a3a8c072de3ea734076a2 (diff) | |
| download | unf-legacy-1c9978010c2616ec664d9febc14beb1625f5f903.tar.zst | |
fleet/modules/public-inbox: fix permissions issue
It turns out the strange behaviour we were observing was due to createHome applying an overly-restrictive mode to the public-inbox top-level directory. This prevented public-inbox-httpd from accessing any of the inboxes, despite it having the correct group assigned. This fixes: - Inbox descriptions showing up as "($INBOX_DIR/description missing)" - Inbox pages only containing the text "No messages, yet" - Mysterious "fatal: not a git repository: '/path/to/inbox'" errors - Probably even more things that I simply didn't notice Change-Id: Ia5a3d57546efd2d0375528fa10e4e979d155b045
Diffstat (limited to 'fleet/pkgs/group-readable-archives.patch')
0 files changed, 0 insertions, 0 deletions