Re: Want to set up SVN for a web app

Bob Archer wrote:
>> Fifth step is to make these changes available to public.
>> Here is the problem.
>> 1. Making public server another (readonly) working copy... not wise.
> It
>> 2. Continuous export's of the whole directory tree... not wise.
> Projects
>
> What about:
>
> 3. rsync (or ant or...) from your build server or other workstation that
> does have a working copy. This should be set up to exclude the .svn
> files and any .template type files you might use.

Just be careful to think about 'which' working copy you use. One of the
nice things about version control systems is that they can permit
concurrent operations with older and newer revisions at the same time.
You may want a separate working copy just for this purpose so it can be
pointed at specific tested/approved revisions or tags at the same time
ongoing work is being added and tested in other areas.

-- 
   Les Mikesell
    lesmikesell_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1521536
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].