user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Alyssa Ross <>
Subject: public-inbox-init with minimal info
Date: Thu, 03 Oct 2019 11:16:01 +0000	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]

In NixOS, the best way for us to provide a public-inbox module would be
to generate the configuration file ahead of time, and then initialize
inboxes that don't already exist at some reasonable time during boot.

public-inbox-init tries to write a config file in addition to
initializing an inbox.  My initial idea was to just eschew
public-inbox-init for doing git init --bare myself, which works great
for V1 repositories, but I'd really like to be generating V2 ones.

Since the V2 initialization isn't encapsulated in one easy command, I'm
wondering what the best way to accomplish initialization without writing
a config file or asking for unnecessary information is.  I could just
run public-inbox-init with PI_CONFIG=/dev/null, but then it's still not
clear to me what information about the mailbox the script requires to be
able to initialize the mailbox.  Looking at the code, I see that at
least the primary address is passed to PublicInbox::Inbox, but I'm not
sure what that would actually be used for inside the inbox.

So, what would the best thing for me to do here be?  To summarise, I'd
like to generate V2 inboxes while providing as little information about
the inbox as possible, and without writing a config file.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

             reply	other threads:[~2019-10-03 11:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-03 11:16 Alyssa Ross [this message]
2019-10-04  2:45 ` public-inbox-init with minimal info Eric Wong
2019-10-04 11:18   ` Alyssa Ross
2019-10-05  5:14     ` Eric Wong
2019-10-05 13:05       ` Alyssa Ross
2019-10-05 19:58         ` Eric Wong
2019-10-06  9:52           ` Alyssa Ross
2019-10-06 12:01             ` Eric Wong
2019-10-07 20:52               ` Alyssa Ross
2019-10-08  7:11                 ` Eric Wong
2019-10-09 12:09                   ` Alyssa Ross
2019-10-10  8:19                     ` Eric Wong
2019-10-16 10:04                       ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).