[volunteers] gruyere (Linode host) upgraded
daniel at gimpelevich.san-francisco.ca.us
Wed Jun 25 12:47:03 PDT 2008
Rick Moen <rick <at> linuxmafia.com> writes:
> Quoting Warren Turkal (wturkal <at> gmail.com):
> > The closest FHS gives is a recommendation is to locate the document
> > root somewhere under /srv.
> Yes, but by that point, Dan was getting pretty silly with some of the
> newer inventions, and nobody I respect has yet followed his lead with that.
> FWIW, our httpd document root on gruyere is under /var/www, which is
> hardly ideal but at least is a place webmasters will expect it. Web
> Team people will probably just symlink to it from their homedirs.
> > One positive of moving to SVN is that the other SCMSs generally have a
> > decent tool to import revision history from SVN. Imports from CVS or
> > RCS are usually less reliable in my experience.
> Fortunately, we do not yet have significant revision history, so we have
> opportunity to pick a best-suited tool, as opposed to merely one we can
> depart from without lossage.
> (Anyway, it's 2007. Who in his right mind would do a new deployment of
> CVS, or start using RCS for anything that matters?)
Well, the site docs and the whole website and SVN tree are now indeed in /srv.
That's right: With all the web-team list posts that got copied to the
volunteers list, none of the posts dealing with the migration or the DNS
repointing were among them. I had briefly forgotten about the existence of the
web-team list, so when I saw that there was no mention of this on the
volunteers list, I thought the repointing may have been accidental, and was
about to fix that yesterday, when I suddenly remembered the web-team list and
read its archives. This was all prompted by a report that the Netiquette page
(on the Linode) still had a link to the IRC page, which was now a 404.
Apparently, it was somehow skipped during the initial SVN import. It's there
now, minus the workaround for the old server's crufty old Apache. When I issued
the SVN commit, SVN complained that the post-commit script exited with an
error, with a blank error message. In looking to see why, I found that the
script is itself blank. It should also be noted that one needs a password for
SVN separate from the login password even to issue the commit (but not the add,
apparently), and this password must be stored in a plaintext password file.
Upon adding myself there with a password that can be easily found on the web, I
briefly considered not bothering and using Lisa's username and password
instead, since that was the only one already there. All in all, in the short
term, the website is in perhaps an even more precarious state.
On a related note, do we need yet another recap on the state of the 9008 JBOD?
The use for it I talked about when I came back from SCALE is still ideal.
More information about the volunteers