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: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.3 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id EF2081F5AE for ; Fri, 23 Apr 2021 20:13:03 +0000 (UTC) Received: by mail-qt1-x834.google.com with SMTP id s4so9507622qtw.3 for ; Fri, 23 Apr 2021 13:13:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:subject:message-id:mail-followup-to:mime-version :content-disposition; bh=YQFZSTdNoIzhNlrC00Pz77ZEY5tE6BhnkqnZQflV7pw=; b=Q85nDiPQZyj6DslqRFv3IESLQ+N3iulbPyb/ABH8+dNPtSKxqIgmO+uTv2LjdyMO3j NM8P9rx1s0GuOlzwz3JDsxkY+NKH0mb03iHOgKwoCUo9+/9hN9gYmTWY5OMvwxg+FMtj dFcwgDH1IA8FvJtR9QFWR9lVoMTiky2NjpRjU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to :mime-version:content-disposition; bh=YQFZSTdNoIzhNlrC00Pz77ZEY5tE6BhnkqnZQflV7pw=; b=IoY4KC7lfTDmMe00yt+Ljpm8LaD3uCjjnQXr7wlxFK20Cv0opigax7y+H3Bx8JwDFN QZJpmVjucNv5mdDFKk5mIgW4iLIAwgBFF8LXMvnKS8dhxjHVL5UN3jNBNC1JjY8z6m23 AnDTMKA/eJ2OzfezTRp4oAeSiIQdEWJU5JGTIU8pWcNKLTjxoRdGtbtwx6ATkg+Ml5FQ zxi8cI4Z+i/fXdXHXHv7z59nWOJeIuOsHa5bshfROjtAXStfaI+LUsRUltD/z+ggpi0U DiqfWTeyUNtgK5UybdHeP7dzPkwuy65dxOGWHovhJ2T12Y3Y44to4BfFr72r1NbJCwue FB2A== X-Gm-Message-State: AOAM533GZZ998poudd5ZfdESN1z5itITFHFkJbo74e9M0Er7xaMw7AhJ zLmbWTwfjr0reqZRXYNaYv7UykqM9GnxNYz7 X-Google-Smtp-Source: ABdhPJyS/X89qhGxka7yjdy/a1TOt+NG09SRGnFu8nUFPxQ7CEPh+xIBaHh4jVgps9kFI+jDv4/s9w== X-Received: by 2002:ac8:584f:: with SMTP id h15mr5539569qth.97.1619208782303; Fri, 23 Apr 2021 13:13:02 -0700 (PDT) Received: from nitro.local (bras-base-mtrlpq5031w-grc-32-216-209-220-18.dsl.bell.ca. [216.209.220.18]) by smtp.gmail.com with ESMTPSA id i2sm5302589qtg.0.2021.04.23.13.13.01 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 23 Apr 2021 13:13:02 -0700 (PDT) Date: Fri, 23 Apr 2021 16:13:00 -0400 From: Konstantin Ryabitsev To: meta@public-inbox.org Subject: Setup pointers for extindex and /all Message-ID: <20210423201300.qdvaaxacp2f6rfy7@nitro.local> Mail-Followup-To: meta@public-inbox.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline List-Id: Eric: I'm working on the new incarnation of lore.kernel.org (that will run on multiple frontends as opposed to the centralized version we have now) -- I hope to have everything ready to go by the time 1.7.x rolls out. I wonder if you can give some pointers for extindex and /all, specifically: - what needs to go into the config file to enable the feature? I poked at the source, and it appears that this will do it?: [extindex "all"] topdir = /path/to/where/xap15/will/live - when "public-inbox-index" runs in grok-post script, will it automatically update the "all" extindex without any additional flags, or do we need to pass something special to it? - when handling message-id based lookups, will the "all" extindex be used automatically, if found? Thanks in advance! -K