From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <lkcl@lkcl.net>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN: AS20860 217.147.80.0/20
X-Spam-Status: No, score=-3.1 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2
Received: from lkcl.net (lkcl.net [217.147.94.29])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by dcvr.yhbt.net (Postfix) with ESMTPS id 601621F466
	for <meta@public-inbox.org>; Tue,  4 Feb 2020 18:43:11 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lkcl.net; s=201607131;
	h=Content-Type:To:Subject:Message-ID:Date:From:MIME-Version; bh=GAFCIUTIj9yajq51nLH6M5o6fsP1fY6ix0Jjw7MHySE=;
	b=QNhCkXW/FNuXgaWD2nzfI1x4zEyL3aKFPFxBP3H/E3RSwAnNlzVFruLeZh/cPKrd4uEJrlfK/39Rb7izeYMk5rH54zfkLugU6DLV+tJMHx/9qSRdgLfN70OLMbVjZXeShQvAdmlSOl38jMyb9J32wocW/TWvUGoYEw42a9XpnD8=;
Received: from mail-lf1-f53.google.com ([209.85.167.53])
	by lkcl.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
	(Exim 4.84_2)
	(envelope-from <lkcl@lkcl.net>)
	id 1iz3AC-0003D9-Qc
	for meta@public-inbox.org; Tue, 04 Feb 2020 18:43:08 +0000
Received: by mail-lf1-f53.google.com with SMTP id z18so12951080lfe.2
        for <meta@public-inbox.org>; Tue, 04 Feb 2020 10:42:53 -0800 (PST)
X-Gm-Message-State: APjAAAW4F+cidczXe8bqaIFtxGOI+RKDR+N+SDt/hOAlwJdhkk7hQiM2
	wQelwbxegKYiBin02mY3EnHMNIvdWyw8tuj60Wg=
X-Google-Smtp-Source: APXvYqxYUEpVCOM0nhMpFBjhyG7E4jD7bjxSX58910kGMb99NqsrxppaYSERgz97L4q2STGlyQKEGwzVJdtf2UMZcp4=
X-Received: by 2002:a19:c82:: with SMTP id 124mr15471947lfm.152.1580841767811;
 Tue, 04 Feb 2020 10:42:47 -0800 (PST)
MIME-Version: 1.0
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Date: Tue, 4 Feb 2020 18:42:36 +0000
X-Gmail-Original-Message-ID: <CAPweEDz9wN+OO9twe3JJFYgi2_3yD+9X4s9Z0g2Hqjyf2F8=JA@mail.gmail.com>
Message-ID: <CAPweEDz9wN+OO9twe3JJFYgi2_3yD+9X4s9Z0g2Hqjyf2F8=JA@mail.gmail.com>
Subject: setting up mailman-to-atom-converter then atom-to-public-inbox
To: meta@public-inbox.org
Content-Type: text/plain; charset="UTF-8"
List-Id: <meta.public-inbox.org>

hi, just as the subject says, i'm currently modifying mailman_rss to
support atom and would like to set it up on libre-soc.org shortly.

firstly: very grateful that public-inbox even exists, it is kinda
important to have really, really simple offline archives of project
mailing lists.

second: i have no idea how to go about setting it up :)

third: sigh, i have two unknowns (three), because i am actually
modifying mailman_rss to support atom, *and* i would prefer not to
overload my server by splitting up the creation of atom feeds into
multiple separate processing sections (by month) *and* i have no idea
if public-inbox can support feeds-of-feeds.

to explain / unpack that: here's how i would envisage the workflow so
as to minimise the server load:

* cron job goes through the monthly mailman archives *by month*
performing a re-creation *only* of the latest month's atom feed
* same cron job adds to a "global" atom file containing "links to the
monthly atom files"
* public-inbox sees that list-of-monthly-atom-files
* public-inbox walks the "tree" of monthly atom files, grabbing each one in turn
* public-inbox loads all messages from all monthly atom files.

is this possible or does public-inbox expect one whopping monster
resource-hogging beast-of-an-atom-file potentially hundreds of
megabytes long?  (the reason i ask all this is because the server i am
running this on only has 1GB of RAM and i'm not going to be upgrading
it as it costs money).

tia,

l.