>> >> 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. > 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. 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.