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

RE: subversion - readonly copy

From: Gavin Lambert <colnet_at_mirality.co.nz>
Date: Tue, 5 May 2015 16:41:06 -0700 (PDT)

On 5/05/2015 22:42, Lilian Skov wrote:
> I store our Standard Operation Documents and Working Instructions in
> subversion. For editing I have a specific area to check-out, modify and
> check-in. This works fine.
> However for other users to READ the documents, I keep a supposedly
> read-only copy of the file-structure and documents on another server. I
> generated this by use of Tortoise SVNàExport.
> My question is: how should I update specific documents in the read-only
> folder, when changes have been added to specific documents in
> subversion? If I use Export, the system generates a new folder.

Unless there's some reason why you don't want a .svn folder to exist in the read-only copy (eg. space constraints or tools that get confused by its presence), then the best way to handle this is to set up an account on your server that only has read-only access to the repository, then check out a working copy as that user.

You can then simply "svn up" either manually or as a scheduled or hook task to keep this copy up to date.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-05-06 01:41:13 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.