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: AS11403 66.111.4.0/24 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id A3D631F4BE for ; Wed, 9 Oct 2019 12:09:11 +0000 (UTC) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id D34C622220; Wed, 9 Oct 2019 08:09:10 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 09 Oct 2019 08:09:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alyssa.is; h= from:to:cc:subject:in-reply-to:references:date:message-id :mime-version:content-type; s=fm1; bh=26gUQlSYenLvbBezL/aS6pyCBN SVqKbJ9SCV1wQwe1I=; b=E0RoOZM/HAG/i4zlrSp2XrekaWn4tDgZj+uVmlWY5O 2amJhAToLa93SSuxd12vawmTAkSbm0rn2SIe6Ln5cIpElc1HtdRAYPYaXQpK5I0S DXem1ZQyQQ5js9LVjmARN61RRgWRKQ3ciPV/gS2lrF/Fh8BfE172gV7VUlywyQpP 4TLQbeliIIhC2PMJAbA49LinbT0wnItUsTTStJRmI0MRUhzJZ23ix31ibXqyr8gJ 0z1npo7HCJ60XLf/g83qw0WpB/vnvLcznXGBF/Qqa+KyjWTD2HSVh97s5xxOqUEQ VRgwGiFJ2r0PkemxHJiR8wCHQbdErQtePaINi3lnnR1w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=26gUQl SYenLvbBezL/aS6pyCBNSVqKbJ9SCV1wQwe1I=; b=Lp6BmHndO8xM7iVZCElFGa KL9kbf/wHNRjfC2Go4urzdBSZcHggEok/P2+2eT56XWJz4dKaKT4srfx2SVqWNrY H+5hUMlLjlp5gavfJn6AoTcLg9M2XsvvOn+LbjUdUxK01BpkFh1ZVyf1WGOPBcnK gzkEnOdgWBSdwRGelDkxgCDdVGkzqIECSZdPvFdfj3ZllLOtyrvAX1T58HlSPz9T gsYoniQkmbE+v9cz2/VGZ7xYmpzxnM7niW7mO7gnRaDCy+MoCQvv/4dJYbDqzUDJ CpBeyXJkK8lBUp3bmqoTamsn+aoeQ6UaWWxOi3nsNicbrAq8ZnGxEKidbO8zzkYw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedriedugddvhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephffvufgjfhffkfggtgesghdtreertd dttdenucfhrhhomheptehlhihsshgrucftohhsshcuoehhihesrghlhihsshgrrdhisheq necuffhomhgrihhnpegvgigrmhhplhgvrdhorhhgnecukfhppeekuddrudekjedrvddvge drudeftdenucfrrghrrghmpehmrghilhhfrhhomhephhhisegrlhihshhsrgdrihhsnecu vehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from localhost (130.224.187.81.in-addr.arpa [81.187.224.130]) by mail.messagingengine.com (Postfix) with ESMTPA id 2B8D78005B; Wed, 9 Oct 2019 08:09:10 -0400 (EDT) From: Alyssa Ross To: Eric Wong Cc: meta@public-inbox.org Subject: Re: public-inbox-init with minimal info In-Reply-To: <20191008071101.GA28837@dcvr> References: <87bluyhyfi.fsf@alyssa.is> <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> Date: Wed, 09 Oct 2019 12:09:04 +0000 Message-ID: <874l0ice8v.fsf@alyssa.is> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" List-Id: --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable >> >> services.public-inbox.http.mount =3D "/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... >>=20 >> "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. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEH9wgcxqlHM/ARR3h+dvtSFmyccAFAl2dzeEACgkQ+dvtSFmy ccAgGA//Um90KP3uebCIJz1gJxo59P+i3K6XQv5aFeelXdHrCUItf4isAc+msYXu YPQcn/CUU/NiUxd/E7HKEHrvRRnfduCZCiGRtW5fkH2KR/8cjIyqkIDlfCn6eMY2 DlngkyEACZc7CByAqimIxqWT23Y9IEMXLRpGAtplwir6u6M0wojFPt1120KBlxgg PpcO/QrhAmSR/zZ7CcNvcskfPQtOcjqPMt6qws2lCC9kJCAx403YocnKmleO/xev YqUzHnaWd4ugHTzN8QHmHnbKQqVpRXnGIrA6veuUbsq1Cmp4A/I0I9f3PtzRNEY6 RJTw+pAgX9mAKqw6S0a9rV7Bzl9h+rn50AchNF4IMta9d1aRih6GJNtJ/+KDxYiC hm+Og1YDF13eEATriSG5b2jWonWL6gCLNQwFoQvWDPu7kvZkZ86sJ/3NJJehNB2q Nj9L0sK5+lFovWMj4gYsEAcPLXtTuTlwXYIUt4yaP4RY9vsmb+b14Ig4sYw7JqM2 vCWRQ3CQxe6bWpPVw+XDG9Qu3nWWIDvHj9DcpNxwzw+Hp+86JBtkAF3RDup0IRWb cZOWTW6y7g6EA38zN2/qa+ZFiHH834AVqGncr543gAt5K31jYxmY9NzmgvsI4F2r bBaBGrAjkmojc2oqYoDdepKfZ+Ksn8Ym4ev36w34Bqhaehk+kxs= =B8Xt -----END PGP SIGNATURE----- --=-=-=--