[GLLUG] Subversion & Bug Tracking Panel

[Richard Houser]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> From: Charles Ulrich
>> Because they don't allow cron jobs or because they don't allow
>> subversion?
>> Is there any particular reason you have it auto-updating every 15
>> minutes instead of manually whenever you make a change?
>
> These are three Windows servers within the DMZ and off the NT domain.
> Pulling updates from the web server was a quick solution to permission and
> firewall hurdles. Definitely not a perfect solution and one I hope to
> re-address soon through a hook script and probably mapped drives.
>
> Though there was one recent side benefit, when concerns were raised about
> the threat of web site defacement, I was able to confidently say we had that
> issue covered. I spared them the fact that if someone was able to deface the
> web site, we would have bigger issues than what the web site looked like.

Pulling seems like a very inefficient way to handle it.  I think you
should really look at pushing the data out.  I'd recommend something
like an rsync update (via ssh) to each server triggered when a commit is
made.

Rsync has the benefit of transferring little more than the changes, is
fast, one of the more common file transfer protocols, and can also
repair anything that happens to your site just like your svn setup now :).

If the pull from a repository is required, you can always export to CVS
if subversion is specifically banned for some reason.

You get major bonus points if you deploy the page to an http server
instance on the repository machine and check it for XHTML/CSS validation
prior to allowing the commit :).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFF8I1UUMkt1ZRwL1MRAmX4AJ9Yrp3h+XqSuiU0fzCFSSf44itHuQCePkZE
A6//Vb68vCIAjbQ63kL89xY=
=W95p
-----END PGP SIGNATURE-----