From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: "Frank Ch. Eigler" <fche@elastic.org>,
Julian Seward <sewardj42@gmail.com>
Subject: Re: Hosting www.valgrind.org on sourceware
Date: Sun, 17 Oct 2021 15:28:10 +0200 [thread overview]
Message-ID: <YWwk6owQYUk5WoIu@wildebeest.org> (raw)
In-Reply-To: <YUshJf6Ff4pbPn1O@elastic.org>
Hi,
On Wed, Sep 22, 2021 at 08:27:24AM -0400, Frank Ch. Eigler via Overseers wrote:
> > Would it be OK for me to set this up? I can create the valgrind-
> > htdoc.git and hooks myself. Julian can update DNS to make valgrind.org
> > and www.valgrind.org a CNAME for sourceware.org. I might need some help
> > with apache vhost and the Let's Encrypt for https setup.
>
> Who can say no to someone volunteering to do the work! Welcome.
I finally managed to do this. I added valgrind-htdocs.git with hooks
to checkout the tree in /sourceware/projects/htdocs on post-update.
https://sourceware.org/git/valgrind-htdocs.git It has all the commits
from the old svn repo except for the various tar.bz2 archives under
downloads because they bloated the repo and most of them are under
https://sourceware.org/pub/valgrind/ those which weren't are now under
https://sourceware.org/pub/valgrind/archive/ they are very old.
I added /etc/httpd/conf.d/sourceware-vhost-valgrind.conf which mainly
contains redirects from http to https and www.valgrind.org to
valgrind.org. I bootstrapped a valgrind.org certbot certificate using
valgrind.wildebeest.org (the test site), once DNS are changed we can
add valgrind.org and www.valgrind.org to it.
Because php is used inside .html pages and there is a header.php and
footer.php that are required to be included in every page I also
created a separate php-fpm pool as /etc/php-fpm.d/valgrind.conf. This
creates a valgrind.sock that the vhost uses so it doesn't interfere
with any other vhost using php.
The results can be seen at https://valgrind.wildebeest.org/
Julian, if you think this looks good, could you set valgrind.org and
www.valgrind.org as CNAMEs to sourceware.org ? Then I'll update the
letsencrypt certificates so https works as expected.
Cheers,
Mark
next prev parent reply other threads:[~2021-10-17 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 12:15 Mark Wielaard
2021-09-22 12:27 ` Frank Ch. Eigler
2021-10-17 13:28 ` Mark Wielaard [this message]
2021-10-17 14:33 ` Frank Ch. Eigler
2021-10-17 19:30 ` Christopher Faylor
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=YWwk6owQYUk5WoIu@wildebeest.org \
--to=mark@klomp.org \
--cc=fche@elastic.org \
--cc=overseers@sourceware.org \
--cc=sewardj42@gmail.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.
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).