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 6AFF420248; Tue, 26 Feb 2019 23:19:07 +0000 (UTC) Date: Tue, 26 Feb 2019 23:19:07 +0000 From: Eric Wong To: Mateusz =?utf-8?Q?=C5=81oskot?= Cc: meta@public-inbox.org Subject: Re: Mirroring mailing lists directly Message-ID: <20190226231907.l7y5arqx6pp2nidt@dcvr> References: <20190223031048.GA7084@dcvr> <20190223220738.s5cij5pkqx7ke7ij@dcvr> <20190226175440.zni6w3fcmgz46gbm@DEV604.cadcorp.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20190226175440.zni6w3fcmgz46gbm@DEV604.cadcorp.net> List-Id: Mateusz Łoskot 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...