Re: no inboxes, yet

["Hipólita Yarona" <hipyarona@gmail.com>]

On Mon, Dec 23, 2024 at 5:13 AM Eric Wong <e@80x24.org> wrote:
>
> Hipólita Yarona <hipyarona@gmail.com> wrote:
> > It seems that public-inbox-httpd serves an index that right now looks like
> >
> > ----------------------------------------------------------------------------------------
> > no inboxes, yet
> > <hr>
> > This is a listing of public inboxes, see the `mirror' link of each inbox
> > for instructions on how to mirror all the data and code on this site.
> > ----------------------------------------------------------------------------------------
> >
> > I cloned this very mailing list and I have been using it just fine.
> > How can I make this inbox index be populated?  I thought I'd see the
> > inboxes I have listed in my config:
>
> The default is to not display a list of inboxes (since this
> project was created and maintained by a shy introvert who hates
> promoting anything they do :x)

I totally understand you. :) I wouldn't say I'm an introvert, but I
try to keep a low profile myself as much as I can.  By the way, I read
your marketing.txt---it makes public-inbox a pretty serious endeavor.
While we are here, perhaps I should share that I've seen public-inbox
a long while ago (but only recently had the opportunity to learn how
to use it) and what attracted me to it is the graphical design of the
archives.  Looking into it, I was also very pleased with how it's been
designed and its principles---such as decentralization.

> > # cat ~hip/.public-inbox/config
> > [publicinboxmda]
> >         spamcheck = none
>
> I think you need to set:
>
> [publicinbox]
>         wwwListing = all
>
> (or `match=domain' instead of `all') if you host multiple
> domains off one instance and want to keep them isolated
> in the listing.
>
> See public-inbox-config(5) manpage for more info on
> `publicinbox.wwwlisting' config knob.

Thank you!

> > [publicinbox "meta"]
> >         address = meta@public-inbox.org
> >         url = https://public-inbox.org/meta
>
> Fwiw, that URL should probably point to your domain.

Indeed.  Thanks!