From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/10846 Path: news.gmane.org!.POSTED!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: musl new-year's infrastructure resolutions Date: Mon, 2 Jan 2017 00:40:28 -0500 Message-ID: <20170102054028.GZ1555@brightrain.aerifal.cx> References: <20161231233747.GV1555@brightrain.aerifal.cx> <58698490.4040904@adelielinux.org> <20170102023139.GX1555@brightrain.aerifal.cx> <5869E5E5.4080400@adelielinux.org> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1483335644 3990 195.159.176.226 (2 Jan 2017 05:40:44 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 2 Jan 2017 05:40:44 +0000 (UTC) User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-10859-gllmg-musl=m.gmane.org@lists.openwall.com Mon Jan 02 06:40:40 2017 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1cNvMM-0000FM-Ju for gllmg-musl@m.gmane.org; Mon, 02 Jan 2017 06:40:38 +0100 Original-Received: (qmail 5934 invoked by uid 550); 2 Jan 2017 05:40:41 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 5913 invoked from network); 2 Jan 2017 05:40:40 -0000 Content-Disposition: inline In-Reply-To: <5869E5E5.4080400@adelielinux.org> Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:10846 Archived-At: On Sun, Jan 01, 2017 at 11:32:21PM -0600, A. Wilcox wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On 01/01/17 20:31, Rich Felker wrote: > > On Sun, Jan 01, 2017 at 04:37:04PM -0600, A. Wilcox wrote: > >> On 31/12/16 17:37, Rich Felker wrote: > >>> Adopting an issue tracker. This requires actually selecting > >>> one and setting up the infrastructure for it. The wiki could > >>> possibly be moved to the same infrastructure. (I want to keep > >>> webapp-ish stuff like wiki, issue tracker etc. off the server > >>> that hosts git and release downloads because anything > >>> interactive is a significant attack surface that puts integrity > >>> of code as risk.) > >> > >> Are you looking for hardware, or for admin volunteers? No matter > >> how much I hate wearing the admin hat, I seem to be pretty good > >> at running stable Bugzilla servers, if that's something you are > >> interested in. It's one of the most flexible of the FLOSS issue > >> trackers. > > > > Given how things turned out relying on a volunteer admin for the > > wiki, I'm probably more looking for someone with experience setting > > the chosen tracker up so that I don't have to figure out > > everything myself. I'm familiar with and like Bugzilla from a user > > side, but IIRC it requires some ugly legacy hosting infrastructure; > > is this correct? (I.e. does it need particular old-fashioned > > server/db sw like Apache, Mysql, etc. or can it be used with more > > modern alternatives?) > > I disagree with calling Apache 2.4 "old-fashioned" - mpm_event works > quite well - but it is just good simple CGI. It can run anywhere Perl > can. For an httpd oriented towards dynamic content/"web apps", probably nginx, but if simple CGI is all it needs, I'd just go for something fast and light like thttpd. > It supports MySQL/MariaDB, PostgreSQL, Oracle, and SQLite3. While I > prefer pgsql over the others, I'm not sure I would call any of those > "old-fashioned" either. Postgres or sqlite would be my preference, with a bias towards the latter if there's no strong reason not to use it, simply because I prefer having everything in the filesystem and governed by unix permissions rather than having to deal with separate databases. > Assuming this isn't acceptable, what do you consider "modern"? I think it's fine... > Unfortunately I have experience with over a dozen issue trackers, so I > can likely match you to *something* that would work for your > infrastructure. ...but I am interested in whether you have others that would be worth considering. Rich