Versioning is reasonable because of two main reasons:
- If many developers work on the same code then everybody can develop the code independent on other developers.
- If something went wrong the we can recover to an older version of the code and see who has done what changes and why.
To start developing a new web system that bases on our o-cms, it is reasonable to copy the code of a present system that has the newest developments. The following steps are needed: 1 Making a folder for the new project:
cd /svn/ sudo mkdir [project]
2 Making a new repository:
sudo svnadmin create /svn/[project] sudo chown -R www-data:subversion [project]/ sudo chmod -R g+rws [project]/
3 Changing the Apache's access to that repository in dav_svn.conf:
<Location /svn/[project]> DAV svn SVNPath /svn/[project] AuthType Digest AuthName "repository for [project]" AuthDigestProvider file AuthUserFile /svn/passwd Require user [user] <LimitExcept GET PROPFIND OPTIONS REPORT> Require valid-user </LimitExcept> </Location>
4 Putting a password for accessing that repository via Apache:
sudo htdigest passwd "repository for [project]" [user]
5 Restarting Apache in order to affect the changes.
6 Checking out the old project as a new project.
7 Disconnecting the new project from the repository with deleting all the SVN information.
8 Sharing the new project into the created repository.
9 Commiting the new project into the created repository.
How to put the system to the testserver for testing purposes?
- On the test server, there is a file called passwd in the folder projektid. That file contains all