Andrew,<br><br><div class="gmail_quote">On Tue, Feb 23, 2010 at 3:01 PM, Andrew Berry <span dir="ltr"><<a href="mailto:andrewberry@sentex.net">andrewberry@sentex.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
</div>I would suggest having Subversion working through Apache, then you can access the files via HTTP. Later versions (1.5? 1.6?) support accessing revisions by HTTP as well. Then you can also use Apache modules for access control.<br>
</blockquote><div><br>You bring up an interesting approach I didn't think of. In my case, checking out the files locally and keeping them updated by a cron job is not a problem. I think accessing local files would be faster than accessing a remote server via HTTP. Interesting solution if you want to go lightweight and not have to worry about maintaining a local check out. I guess what you meant re access control is that you can use logged in user information to grant them access to pages?<br>
<br>Steph.<br></div></div>