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,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 870B81F463; Wed, 25 Sep 2019 19:45:03 +0000 (UTC) Date: Wed, 25 Sep 2019 19:45:03 +0000 From: Eric Wong To: Konstantin Ryabitsev Cc: meta@public-inbox.org Subject: Re: Git-only operation mode Message-ID: <20190925194503.GA21501@dcvr> References: <20190925182431.GA4628@chatter.i7.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190925182431.GA4628@chatter.i7.local> List-Id: Konstantin Ryabitsev wrote: > Hello: > > Is there a way to run just the archiver component of public-inbox -- just > writing to git repos without any of the indexing/frontend bits? One of the > idle conversations I had with vger.kernel.org folks was to see if we can > shift the source of truth archive generation to happen at their end. We > would then clone repositories from them and provide the frontend/search bits > on lore.kernel.org. From my cursory looking, it would seem that the > watch/delivery tools always expect to be taking care of xapian/indexing, but > I think being able to decouple git bits from search/frontend bits would be a > useful mode or operation. v1 was git-only (that led to scalability problems from big trees). v2 needs SQLite to do dedupe with indexlevel=basic, but not Xapian, anymore. We could get rid of dedupe for v2, but I'm not sure it's worth it...