#publicinbox — Public Fediverse posts

So today I failed to configure #anubis in front of #publicinbox on #nixos

I try to set up a #nixos host with a #simple-nixos-mailserver and #publicinbox and test the whole thing with a nixos VM test.

But I fail hard to get the very basics working - right now making public-inbox behind a nginx reverse proxy available (curl'ing the site returns 404).

Has someone done this before and some nix code I can look at?

I ask this every now and then here: has someone a #nixos #mailserver #snm setup for #mailinglist #mailinglists with #publicinbox (the software, not the concept) that they can share?

I ask this every now and then here: has someone a #nixos #mailserver #snm setup for #mailinglist #mailinglists with #publicinbox (the software, not the concept) that they can share?

I ask this every now and then here: has someone a #nixos #mailserver #snm setup for #mailinglist #mailinglists with #publicinbox (the software, not the concept) that they can share?

I ask this every now and then here: has someone a #nixos #mailserver #snm setup for #mailinglist #mailinglists with #publicinbox (the software, not the concept) that they can share?

I ask this every now and then here: has someone a #nixos #mailserver #snm setup for #mailinglist #mailinglists with #publicinbox (the software, not the concept) that they can share?

Has someone a template for setting up simple #nixos #mail #server #snm with a mailinglist (or multiple) and #publicinbox ?

Has someone a template for setting up simple #nixos #mail #server #snm with a mailinglist (or multiple) and #publicinbox ?

Has someone a template for setting up simple #nixos #mail #server #snm with a mailinglist (or multiple) and #publicinbox ?

Has someone a template for setting up simple #nixos #mail #server #snm with a mailinglist (or multiple) and #publicinbox ?

Has someone a template for setting up simple #nixos #mail #server #snm with a mailinglist (or multiple) and #publicinbox ?

Now THAT looks like a tutorial I wanted to have: https://blog.gnoack.org/post/lei/

#publicinbox #lkml #plaintextemail #plaintext #email #gitsendemail

Now THAT looks like a tutorial I wanted to have: https://blog.gnoack.org/post/lei/

#publicinbox #lkml #plaintextemail #plaintext #email #gitsendemail

Now THAT looks like a tutorial I wanted to have: https://blog.gnoack.org/post/lei/

#publicinbox #lkml #plaintextemail #plaintext #email #gitsendemail

Now THAT looks like a tutorial I wanted to have: https://blog.gnoack.org/post/lei/

#publicinbox #lkml #plaintextemail #plaintext #email #gitsendemail

Now THAT looks like a tutorial I wanted to have: https://blog.gnoack.org/post/lei/

#publicinbox #lkml #plaintextemail #plaintext #email #gitsendemail

The documentation of #publicinbox is really bad.

I just cloned the git public inbox, how can I now read it?

Re-reading #email patch workflow stuff and the #b4 and #publicinbox docs and ... maaan... that is the only true way of developing software together in large teams.

I mean, I don't care for your 5 person project, do what you want.

But for large projects, that really is the only way to develop that truly scales.

Maybe, just maybe, #radicle can become the second way of doing that. Right now, it clearly is not (mainly because it is too young), but I still have hope!

That said, #sourcehut is also really nice, but right now I like public-inbox a bit more. I guess you could combine the two, possibly?

#git #github #shithub #gitlab #shitlab

I want to process 4714 message-id's to collect some patch stats for the last year. I could collect with #b4 which uses the #lore archive but I wonder does it cache or will I end up with lots of redundant mbx files? Worse still would I just be hammering an overloaded server? I guess I should check out the #PublicInbox docs.

HTML email. Most #sourceware projects allow it, if there is at least a text/plain alternative.

But #publicinbox is not so forgiving, it only allows plain-text emails, HTML is rejected by default.

So the https://inbox.sourceware.org archive was incomplete.

We now have a filter that removes redundant HTML parts before storing in public-inbox. And we re-imported missing emails to make the archive complete.

But please don't sent HTML email. It will make DKIM verification of your email impossible.

I’m trying hard to love #PublicInbox, or to even just try it out, but I keep failing. To the point I’m not even sure what I’m supposed to get.

I guess I need “public-inbox for dummies”? Suggestions anyone?

#b4 is a handy tool for managing code review via emailed patches. It was designed to work with #publicinbox archives but it works on arbitrary #mbox's as well. #sourcehut supports pulling the mbox for a thread so it works there too!

https://lists.sr.ht/~sircmpwn/public-inbox/patches/20099

who needs github...

https://public-inbox.org/marketing.html hehe... #publicinbox
Example: https://lore.kernel.org/lkml/