From: Eric Wong <e@80x24.org>
To: "Mateusz Łoskot" <mateusz@loskot.net>
Cc: meta@public-inbox.org
Subject: Re: Mirroring mailing lists directly
Date: Tue, 26 Feb 2019 23:19:07 +0000 [thread overview]
Message-ID: <20190226231907.l7y5arqx6pp2nidt@dcvr> (raw)
In-Reply-To: <20190226175440.zni6w3fcmgz46gbm@DEV604.cadcorp.net>
Mateusz Łoskot <mateusz@loskot.net> wrote:
> Meanwhile, if it's nota secret could you tell a bit about
> hosting of the public-inbox.org?
>
> Is this a VPS or a VM solution, a docker container?
> If a container, could you tell where do you host it?
> I'm still looking for options.
I've been using a $20/month VPS since 2008 (USD). Nowadays it's
up to 2 cores, 4GB RAM which is more than I need but I keep
getting upgrades without paying more. Multiple cores definitely
helps, though; especially with SpamAssassin and incoming mail.
I don't give commercial endorsements, but dig/traceroute should
give you info about where it's hosted. If you're mirroring
lists I host, I prefer you host it elsewhere to avoid putting
too much dependency on a single provider or datacenter.
Process setup is:
public-inbox-httpd -> varnish -> yet-another-horribly-named-server (HTTP/HTTPS)
\
>- tor (.onion)
public-inbox-nntpd ----------/
\
`--------(NNTP port 119)
yet-another-horribly-named-server is an experimental GPL-3 Ruby
server which does HTTPS termination and hosts some other Ruby
stuff on the same IP (different vhost). nginx is a more common
replacement and recommended for most sites :)
public-inbox-nntpd should learn TLS anyways, so doing HTTPS from
public-inbox-httpd won't be far off, either. Making varnish
unnecessary is another goal, but could be tougher...
next prev parent reply other threads:[~2019-02-26 23:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 0:35 Mirroring mailing lists directly Mateusz Loskot
2019-02-23 3:10 ` Eric Wong
2019-02-23 21:19 ` Mateusz Loskot
2019-02-23 22:07 ` Eric Wong
2019-02-26 17:54 ` Mateusz Łoskot
2019-02-26 23:19 ` Eric Wong [this message]
2019-02-27 0:28 ` Mateusz Łoskot
2019-02-27 0:41 ` 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=20190226231907.l7y5arqx6pp2nidt@dcvr \
--to=e@80x24.org \
--cc=mateusz@loskot.net \
--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).