Upon completion of this course you should be able to:
Course Prerequisites:
None
Students are expected to have a working knowledge of:
Linux
1. Subversion
1.1 Installing Subversion
1.2 Creating a working directory
2. Configuring Subversion
2.1 Creating a repository
2.2 Configuring authentication and authorization policy
2.3 Configuring accounts and passwords
2.4 Configuring access permissions
2.5 Enabling SVN service
Subversion (SVN) is an open source version control system. It helps you keep track of a collection of files and folders. Any time you change, add or delete a file or folder that you manage with Subversion, you commit these changes to your Subversion repository, which creates a new revision in your repository reflecting these changes. You can always go back, look at and get the contents of previous revisions.
Log into ADM from your Web browser and follow the steps outlined below:
If you wish to create a new working directory, please follow the steps outlined below:
Please first ensure that SSH service has been enabled.
Use an SSH client to log in to your NAS and then enter the command below to create an SVN repository. In the example below we create the repository “repo” in the “SVN” folder of Volume 1.
After creating a repository, you can configure Subversion server authentication and authorization policies, create user accounts/passwords and access permissions.
In the example below we will be creating the user “asustor” with the password “admin”.
In the example below we assign the user “asustor” to the “Admin” group, and give the user Admin read and write permissions.
After completing the following configurations you will be able to enable SVN service and use a familiar SVN client to connect to the NAS and execute text file or code file management.
If you wish to allow your NAS to automatically enable SVN service on system start up, please add the two files below to /usr/local/etc/init.d
Note: Modify the file access privileges of S99svnerve.sh and K99svnerve.sh to 0774. Be sure to grant the [x] (execution) permission of *.sh for the owner.