Ok, thanks, I was hoping I wouldn't have to manually create 110 folders and set permissions, but it is what it is.
On Wed, May 2, 2018 at 4:40 PM, Geoff Rowell <geoff.row...@gmail.com> wrote: > 1. Create the destination repositories. > 2. Configure the destination repository access rights. > 3. Use "svnsync init" on each destination repository. > 4. Run "svnsync sync" on each to copy content. > > On Wed, May 2, 2018 at 4:16 PM, Paul Greene <paul.greene...@gmail.com> > wrote: > >> /data/subversion *contains* the repositories - it is not a repository >> itself. >> >> So, will the /data/subversion/repo01, /data/subversion/repo02, ... >> /data/subversion/repo110 automatically be created, or do I have to make >> them myself? >> >> On Wed, May 2, 2018 at 4:09 PM, Andreas Stieger <andreas.stie...@gmx.de> >> wrote: >> >>> Hello, >>> >>> >>> On 05/02/2018 10:02 PM, Paul Greene wrote: >>> > Prior to running svnsync, do I need to create the same folder >>> > structure on the destination as on the source? >>> >>> no, just an empty, randomly named repository. >>> >>> > i.e. the source has 110 repositories located under /data/subversion. I >>> > have a folder named /data/subversion on the destination as well where >>> > I want the mirror to go. >>> >>> You need to have as many repositories on the far side as you need >>> mirroring for. The on-disk data will look like this: conf db format >>> hooks locks README.txt >>> Each of these is a synchronization unit and needs to be set up >>> separately. svn does not help you above that level, and below that any >>> structure only exists inside the repository tree which is replicated. >>> >>> > >>> > Do I need to manually create all the subversion repository folders >>> > under /data/subversion before syncing, along with the same user >>> > permissions/ownership? Or does subversion automatically create the >>> > folders? >>> >>> Depends if /data/subversion IS the repository, or CONTAINS repositories. >>> >>> Andreas >>> >> >> > > > -- > Geoff Rowell > geoff.row...@gmail.com >
