From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 23DC21F4BD; Thu, 10 Oct 2019 08:19:26 +0000 (UTC) Date: Thu, 10 Oct 2019 08:19:24 +0000 From: Eric Wong To: Alyssa Ross Cc: meta@public-inbox.org Subject: Re: public-inbox-init with minimal info Message-ID: <20191010081924.GA14812@ailurophile> References: <20191004024559.GA24741@dcvr> <878sq0iwt2.fsf@alyssa.is> <20191005051434.GA23947@dcvr> <87pnjb4a1f.fsf@alyssa.is> <20191005195838.nypagsfok24b5odr@dcvr> <87h84m42vc.fsf@alyssa.is> <20191006120104.GA24228@dcvr> <87tv8k5ldb.fsf@alyssa.is> <20191008071101.GA28837@dcvr> <874l0ice8v.fsf@alyssa.is> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <874l0ice8v.fsf@alyssa.is> List-Id: Alyssa Ross wrote: > >> >> services.public-inbox.http.mount = "/lists/archives/"; > >> > > >> > I think all the services would want access to the same > >> > directories, not just httpd (if I'm understanding that config > >> > correctly). Also, httpd/nntpd only need read-only access to their > >> > mount points, in case that affects things... > >> > >> "mount" here is in the PSGI sense, not the file system sense. My > >> public-inboxes are at https://example.org/lists/archives/. Maybe > >> there's a better name. > > > > Ah, so that overrides the Plack::Builder DSL/language. We also > > have an analogous support problem for PSGI vs public-inbox-config, > > so I've been avoiding any overlap between them. > > > > Perhaps "psgi_mount" would be clearer? *shrug* > > I shied away from that because it would only be clearer if you know what > PSGI is, and the module takes care of all of that. I also considered > httpMount, but since it's already in the http namespace that felt > redundant. Maybe "url_mount"? Naming is one of the toughest problems :< > > Btw, would it be helpful if public-inbox provided a linter for > > its config own file? > > Very much so! That would let us lint config files at build time, and > fail the system build if they were invalid, meaning a system could > "never" have an invalid config file. We already do this with nginx -- > the linter doesn't catch everything, but it's wonderful when it catches > something that would otherwise have left you without a working web > server. OK, adding TODO item. > Here's an idea for a lint: I lost most of a day wondering what I had > done wrong, before realising that I was setting mainrepo to all.git, > rather than its parent directory. The name "mainrepo" isn't great, IMO, > but a lint could have accomodated for that. Sorry about wasting your time! Yeah, "mainrepo" is a bad name, especially with v2 :< I guess we can shift to "inboxdir" and keep the old alias indefinitely for compatibility, since there's already INBOX_DIR all over the documentation. I originally intended for each inbox to have another repo for rejected/spam messages; but just put it in PI_EMERGENCY, instead.