[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
번호 | 분류 | 제목 | 글쓴이 | 날짜 | 조회 수 |
---|---|---|---|---|---|
981 | Develop | [c] 단기과정[01/06] sizeof, 실수표현, 메모리, 연산자 | hooni | 2003.04.23 | 6948 |
980 | Develop | [c] 단기과정[01/07] 제어문, 피보나치수열 | hooni | 2003.04.23 | 7429 |
979 | Develop | [c] 단기과정[01/08] 배열, 포인터 | hooni | 2003.04.23 | 7255 |
978 | Develop | [c] 단기과정[01/08] (다차원 + 배열)포인터, void 포인터 | hooni | 2003.04.23 | 7791 |
977 | Develop |
[c] 단기과정[01/08] 과제.. 파스칼 삼각형
![]() |
hooni | 2003.04.23 | 7280 |
976 | Develop |
[c] 단기과정[01/10] 과제.. swap(any data, ..)
![]() |
hooni | 2003.04.23 | 6930 |
975 | Develop |
[c] 단기과정[01/14] 파일 입출력
![]() |
hooni | 2003.04.23 | 6856 |
974 | Develop |
[c] 단기과정[01/14] 피보나치, 파스칼.. 파일입출력
![]() |
hooni | 2003.04.23 | 7106 |
973 | Develop |
[c] 단기과정[01/15] 피보나치, 파스칼.. 링크리스트
![]() |
hooni | 2003.04.23 | 7256 |
972 | Develop |
[c] 단기과정[01/17] 후위연산 스택 계산기..
![]() |
hooni | 2003.04.23 | 7248 |
971 | Develop | [c] 단기과정[01/24] 정렬 알고리즘 | hooni | 2003.04.23 | 6972 |
970 | Develop | [js] 새로고침(refresh)방법과 다른 페이지 바꾸기.. | hooni | 2003.04.23 | 6559 |