| | 9 | There is no need for a Subversion server dedicated to Quattor. SCDB is just one repository from the Subversion point of view. If you already run a Subversion server, you can skip the installation part and go directly to the configuration part. |
| | 10 | |
| | 11 | === Subversion installation === |
| | 12 | |
| | 13 | There are many possible installation options for a Subversion server. The best is to install it as Apache module, anyway. There is no requirement for the Subversion server to run on a Linux machine, even if it is the installation option documented here. You can even choose to use a Subversion server outside of your site, if you think the network connection is good enough. |
| | 14 | |
| | 15 | If you need to install a Subversion server, the easiest is to install Apache and then retrieve the RPMs for Subversion from [http://subversion.tigris.org/project_packages.html Subversion site]. Don't forget to install the Apache module which is in a separate RPM. |
| | 16 | |
| | 17 | After installing, you have to configure the Subversion server. Look at Quattor installation guide on [http://quattor.org Quattor] web site. |
| | 18 | |
| | 19 | === Repository configuration === |
| | 20 | |
| | 21 | For Quattor, you need to create a repository with the standard structure inside it (or inside a branch) : |
| | 22 | * `trunk` : where you make the changes to your running configuration |
| | 23 | * `tags` : used by SCDB administration tool to do deployment |
| | 24 | * `branches` : for alternative developments |
| | 25 | |
| | 26 | You also need to put the hook script provided as part of SCDB (in the `src/utils/hooks` directory) in the `hooks` directory of your repository, on your Subversion server and give this script [`post-commit`) executable permission for Apache user. |
| | 27 | |
| | 28 | |
