user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: lkcl <lkcl@libre-riscv.org>
To: <meta@public-inbox.org>
Subject: up and running, integrated with exim4 mta
Date: Wed, 18 Mar 2020 07:29:49 +0000	[thread overview]
Message-ID: <E1jET9B-0002Vc-1x@libre-riscv.org> (raw)

hi eric we have things running, hooray, i thought you might appreciate
it is a little different
http://inbox.libre-riscv.org/libre-riscv-dev/new.html

http://bugs.libre-riscv.org/show_bug.cgi?id=181

here are attachments for *direct* integration into exim4. rather than
store in Maildir we have a use subscribed to the mailman2 list, where
in the exim4 configs we specifically look out for that user and
run a pipe to public-inbox-mda

a section to disable spam and also adding the listid to the config is
critical otherwise public-inbox-mda fails silently.

regarding the httpd it was a nuisance to set up as there was no error
reporting.  i tracked down in the exammples how to add 3 lines to do
logging, this really should be there by default at least commented out.

also being able to specify the URL for git repos would be handy because
we already run gitweb and git-daemon, the URL is different ane would
need source hacking to specify an alternative.

with the exim4 integration we do not need the cron job. also i set p
a sysvinit darmon 
argh no editing using console mail program sorry
set up a sysvinit daemon to start httpd, no god no way i let systemd run.
will send that example based on start-stop-daemon later.

very much aporeciated even the existence of pbi as it is one of the last
pieces which allows our project to be entirely offline developed via
git backed storage.

l.

             reply	other threads:[~2020-03-18  7:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18  7:29 lkcl [this message]
2020-03-19  3:06 ` up and running, integrated with exim4 mta Eric Wong
2020-03-19  9:41   ` lkcl
2020-03-20  1:18     ` 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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

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

  git send-email \
    --in-reply-to=E1jET9B-0002Vc-1x@libre-riscv.org \
    --to=lkcl@libre-riscv.org \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://80x24.org/public-inbox.git

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).