[development] Publishing data from legacy svn repository

[Andrew Berry]

On 2010-02-23, at 3:46 PM, Stephane Corlosquet wrote:

> I think accessing local files would be faster than accessing a remote server via HTTP.

Yes. For HTTP, if revisions are still being updated, you could cache the response, and when it expires you'll get the latest revision.

> I guess what you meant re access control is that you can use logged in user information to grant them access to pages?

If you didn't want the world to be able to view the repository over HTTP, you can use Apache to restrict access to the Drupal server, or set up htpasswd controls. But, since you can have a local checkout, as long as you don't need specific revisions it's probably the best solution.

--Andrew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2676 bytes
Desc: not available
Url : http://lists.drupal.org/pipermail/development/attachments/20100224/f1434e2c/attachment.bin