SVN main directory sync

UNIX for Advanced & Expert Users
1

I'm quite new to SVN and having configured it based on tutorials from youtube etc, I have it setup like below:

  • User1 and User2 can commit and update using their own passwords,
  • Updates from both user1 and user2 are visible to each other
  • files are shared between both user1 and user2
  • file contents are successfully visible and updated

Now the problem is that the repo I have setup on server side, is not being updated with the contents from user1 and user2, these changes are only visible to users on their windows system ( using tortoiseSVN client )

I had this SVN repo setup using below given command list:

svnadmin create /var/svn_repo


pico /var/svn_repo/conf/svnserve.conf

and add the following:

anon-access = none
auth-access = write
password-db = passwd

Now you'll need to create a password file:

pico /var/svn_repo/conf/passwd
Add a line in that file for your user in the format =

exampleuser = examplepassword

and then

svn mkdir file:///var/svn_repo/d5
svn import /var/www/html/beta/ONE file:///var/svn_repo/d5

Now , I can't see the /var/www/html/beta/ONE is updated with the contents from both User1 and User2, all changes are local to all users,

Any idea, how to update changes on the server side, so that these changes are visible from the browser using apache2 webserver

2

I think you need to regularly run a svn update on the web server.
Setup a cron job to do that automatically.
If you have set a password it becomes difficult: you need ugly tools like expect. The modern way is to use credentials, this is common practice with a git repository. Does the svn repository work with credentials?

3

Hi.

It has been a long time since I worked with subversion. When I set up our repository, I used as reference the book noted below.

The only thing I recall doing on the server after the initial setup was a backup every now and then. The book included perl codes for incremental backups. In our situation, we needed to run svn serve[/ICODE], the small server code that listened for subversion-related requests.

I also used svn on a consulting contract, and, as I recall it was relatively easy when working from the book. I was the only user, however.

While working with svn was a dramatic improvement over cvs , there are a number of version control systems available now, see link to comparisons below.

Good luck ... cheers, drl

Comparison of version control software - Wikipedia

Title: Pragmatic Version control Using Subversion
Subtitle: The Pragmatic Starter Kit -- Volume 1
Author: Mike Mason
Edition: 1st
Date: 2005
Publisher: Pragmatic Bookshelf
ISBN: 0-9745140-6-3
Pages: 224
Categories: software, version control
Comments: Second edition, 2006