[svn] 하나의 SVN에서 멀티 저장소 (One svnserve, multiple repositories)
One svnserve, multiple repositories
A note on how a single svnserve
can serve multiple repositories.
Yellow Dog
Let’s suppose the Yellow Dog project uses Subversion. You’ve set up a Subversion server (let’s give it a hostname svnserver
), created a user svn
, and a repository /home/svn/repository
. Here’s the command you use to start the server:
$ svnserve -d -r /home/svn/repository
Red Bear, Blue Goat
Sometime later, the Red Bear project also decides to use Subversion. This project is unrelated to the Yellow Dog project and therefore needs its own repository. Similarly, we want a Blue Goat repository for yet another unrelated project.
What to do
Here’s what to do.
$ ssh svn@svnserver
$ mkdir repositories
$ cd repositories
$ svnadmin create red_bear
$ svnadmin create blue_goat
Now we should have a directory layout like the following.
+---repositories
| +---blue_goat
| | +---conf
| | +---dav
| | +---db
| | +---hooks
| | \---locks
| \---red_bear
| +---conf
| +---dav
| +---db
| +---hooks
| \---locks
\---repository
+---conf
+---dav
+---db
+---hooks
\---locks
All we need to do is move the (poorly named) original Yellow Dog repository alongside the newer ones. I’d recommend taking down svnserve
first, and of course notifying everyone working on the Yellow Dog project — but the move really will only take a few seconds.
$ killall svnserve
$ mv repository repositories/yellow_dog
$ svnserve -d -r /home/svn/repositories
Inetd mode
If you’re using svnserve
in inetd
mode, most of the above applies directly — you simply adjust thesvnserve
configuration file in the obvious way to reflect the new repository root.
Repository URLs
The new repository URLs are:
svn://svnserver/yellow_dog
svn://svnserver/blue_goat
svn://svnserver/red_bear
Note that the old URL for the Yellow Dog project was svn://svnserver
. This means that anyone with a Yellow Dog working copy will have to svn switch it.
$ svn switch --relocate svn://svnserver svn://svnserver/yellow_dog
Loose Ends
There may be a few scripts kicking around which need to be changed to reflect the new layout:
- the repository backup script
- the Yellow Dog automated build
- any personal build scripts.
Nothing should be hard, but with a very little forwarded planning you’ll see no loss of service. Once you’ve adjusted (if necessary) your backup script, I’d suggest now would be a good time to rehearse the recover-from-backup procedure.
[출처] http://wordaligned.org/articles/one-svnserve-multiple-repositories
-
CentOS 에서 Cacti 설치하기
-
[ios] Xcode cannot run using the selected device
-
인증서 *.p12 파일을 *.pem 파일로 변환
-
[linux] CentOS 에 APM 설치하기
-
[php] mysql_ 과 mysqli_ 의 차이
-
[python][django] request.cookie 읽어오기 ㅋㅋㅋ (쓰기)
-
Laravel 5 Failed opening required bootstrap/../vendor/autoload.php
-
[ios] Pod 특정 버전 설치하고 사용하기
-
[svn] 하나의 SVN에서 멀티 저장소 (One svnserve, multiple repositories)
-
[c] 한글 문자열 출력
-
[ios] @property의 속성 (strong, weak, copy) 사용 경우
-
네트워크 용어 정리