[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: OK, so copy is supposed to work now? (as it still isn't, hehe)

From: Greg Stein <gstein_at_lyra.org>
Date: 2001-12-07 09:54:45 CET

On Thu, Dec 06, 2001 at 01:20:46PM -0600, Karl Fogel wrote:
> "Jay Freeman \(saurik\)" <saurik@saurik.com> writes:
> > OK, I can try to do something like that tomorrow.
> >
> > BTW, how does that, the process of updating the website, work (if
> > someone wouldn't mind explaining, and has the time to, I'm quite
> > curious)? I write up a patch for project_faq.html, send it to the list,
> > and it gets merged. Then, does someone else check it out and upload it
> > to the website, or is there some spiffy Subversion way of having a URL
> > map directly into the HEAD of a repository through the magic of mod_dav?

try: http://svn.collab.net/repos/svn/trunk/autogen.sh

That's the HEAD for autogen.sh. In essence, you can use your Subversion
repository as a live website.

[ there are issues with things like Apache not looking for index.html, but
  we'll get those sorted out later ]

Want some *real* fun? Have people check in/out of (say) /repos/site, and set
of a second Location/SVNPath block to refer to the same SVN repository. On
that Location, turn on Server Side Includes or PHP. Woo!

[ strictly speaking, it might even be possible to do SSI on the actual
  repository because I don't think the SVN client ever does a GET from
  there. Hmm... actually, it does in some cases. But hey... ]

It is also possible to use mod_rewrite to turn /somepage.html into
/repos/project/www/somepage.html

> > Last I can find is back at the end of October when people were asked to
> > commit things to the CVS repository _as well as_ the Subversion
> > repository so the website could be updated... is that still the case?
> > (I am setting up a web page for a project I'm planning on putting in a
> > Subversion repository, and if there is a nice way to automate web page
> > sync'ing I'd love to know about it :-P.)

As mentioned above, you can publish right out of a Subversion repository. If
you believe you're going to have a heavy load, and want to avoid smacking
the Subversion DB on each request, then you can use a hook script to do an
"svn update" on a web-published working copy each time somebody commits
something to the web pages in your repository.

>...
> There is a way of having URLs that map directly to the HEAD in the
> repository, though; maybe we should have some of our links work that
> way. Greg Stein?

We're doing that for some of the "documents" on tigris.org. But the builtin
pages on the site can't really reference stuff from a different box as far
as I know. Thus, the need for a working copy there.

"There is a way" is simple and described above. There is also a way to refer
to a specific revision of a file, but that isn't officially supported except
for a WebDAV/DeltaV client.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:51 2006

This is an archived mail posted to the Subversion Dev mailing list.