I like the revision idea, and you can use that keyword substitution
technique you found. BTW I've set up a cron job to update the /source
from svn every ten minutes (untested). I have a post-commit hook that
can email on commits events... perhaps we should set up a list for
people that want this? I'm fighting a file ownership/permissions
problem that seems to prevent the post-commit hook updating /source
(thus the crob job). Sorry, running around a bit today...
cheers,
David
On Oct 13, 12:07 pm, Eitan Isaacson <ei...@ascender.com> wrote:
> Thanks David!
> "source" is fine, it could also be "demos".
> Just a thought: Could the HTML files that are displayed also show their
> last changed SVN revision? That way automated tests could raise a
> warning if they are dealing with pages they were not recorded against.
> It should be in an easily locatable place, like the beginning or the end
> of the doc with a distinct ID or class name, like "svnRevision".
> I could hack that up once I have SVN access. Just need a yay or nay.
> Cheers!
> On Fri, 2008-10-10 at 21:26 -0700, David Bolter wrote:
> > Hi All,
> > Right now we have:
> > A source browsing site:http://svn.codetalks.org/repos/trunk/
> > Live site for running examples in browser:http://codetalks.org/source/
> > (based on trunk)
> > We can have emails sent automatically when the source repository is
> > updated...
> > Anyways this is just a quick status email... what do people think of
> > this setup? I wasn't sure about "/source" for the live site...
> > cheers,
> > David
