From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: musl new-year's infrastructure resolutions
Date: Mon, 2 Jan 2017 00:40:28 -0500 [thread overview]
Message-ID: <20170102054028.GZ1555@brightrain.aerifal.cx> (raw)
In-Reply-To: <5869E5E5.4080400@adelielinux.org>
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
next prev parent reply other threads:[~2017-01-02 5:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-31 23:37 Rich Felker
2017-01-01 22:37 ` A. Wilcox
2017-01-02 2:31 ` Rich Felker
2017-01-02 2:33 ` Rich Felker
2017-01-02 5:32 ` A. Wilcox
2017-01-02 5:40 ` Rich Felker [this message]
2017-01-02 6:39 ` Khem Raj
2017-01-02 16:58 ` Rich Felker
2017-01-02 18:11 ` Alexander Monakov
2017-01-02 18:23 ` Rich Felker
2017-01-02 18:15 ` Solar Designer
2017-01-02 18:25 ` Rich Felker
2017-01-02 18:27 ` Kurt H Maier
2017-01-02 18:36 ` Rich Felker
2017-01-02 18:52 ` Kurt H Maier
2017-01-02 19:16 ` Rich Felker
2017-01-02 20:06 ` Kurt H Maier
2017-01-02 22:59 ` A. Wilcox
2017-01-02 23:09 ` Kurt H Maier
2017-01-02 19:10 ` Matias A. Fonzo
2017-01-02 19:18 ` Rich Felker
2017-01-02 19:28 ` Matias A. Fonzo
2017-01-03 1:20 ` Laurent Bercot
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170102054028.GZ1555@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).