[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Allura at SF is ready

From: Phil Holmes
Subject: Re: Allura at SF is ready
Date: Wed, 2 Sep 2015 09:29:35 +0100

----- Original Message ----- From: "josiah oberholtzer" <address@hidden> To: "Federico Bruni" <address@hidden>; "Trevor Daniels" <address@hidden> Cc: "Lilypond bug list" <address@hidden>; "lilypond-devel" <address@hidden>
Sent: Wednesday, September 02, 2015 5:19 AM
Subject: Re: Allura at SF is ready

Hi all,

Sorry for being out of touch - other obligations caught up with me.

I'm not sure how to proceed on the bugs.lilypond.org side. The Allura
server there is operational (visit the site to see), but - as Federico
points out - we don't have working HTTPS connections.

It looks like the GNU certificate only covers *.gnu.org domains, which
bugs.lilypond.org isn't. I believe someone suggested renaming the site
something like "bugs-lilypond.gnu.org" or "lilypond-bugs.gnu.org", which
would allow wildcard coverage from the certificate. I don't believe the
change can be made on our end (but I couldn't say for sure). More advanced
Apache-wrangling than what I've managed to get the Allura application
online is outside my knowledge.

I see no reason why "lilypond-bugs.gnu.org" should not be perfectly acceptable. We've been using code.google.com for goodness-knows how long, so another tracker without a lilypond.org domain name should be no problem.

Phil Holmes

reply via email to

[Prev in Thread] Current Thread [Next in Thread]