blob: dfe3cb59b91ad2b93b600501284cab104cf792e6 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
|
RSYNC REPOSITORIES
RSYNC repositories are simple to serve and simple to use. In the repository
directory, there needs to be a '.rsync' file that points to the remote of
the repository. This is used in order to fetch changes from the upstream.
'.rsync' file looks like this for the core repository:
rsync://carbslinux.org/repo/core
RSYNC repositories have some few distinctions when it comes to fetching
them. Unlike GIT repositories, they don't have a defined "root" directory.
When there are multiple repositories in a shared repository (such as the
Carbs Linux and KISS Linux repositories), individual repositories need to
have this '.rsync' file. This doesn't, however, slow down operations.
Fetching from rsync repositories are still considerably faster and smaller.
SETTING UP AN RSYNC REPOSITORY
Carbs Linux repositories automatically sync from the git repostitories
and serve it through the rsync daemon. Here is a sample shell script
that I use in order to sync repositories. Feel free to customize for your
own use.
#!/bin/sh
HOSTNAME=rsync://carbslinux.org/repo
GITDIR=/pub/git/repo
SHAREDIR=/pub/share/repo
git -C "$GITDIR" pull
rsync -aC --delete --include=core --exclude=.rsync \
"$GITDIR/" "$SHAREDIR"
for dir in "$SHAREDIR/"*; do
[ -d "$dir" ] || continue
[ -f "$dir/.rsync" ] ||
printf '%s/%s\n' "$HOSTNAME" "${dir##*/}" > "$dir/.rsync"
done
You can then create an 'rsync' user for serving the repositories.
-> adduser -SD rsync
Create '/etc/rsyncd.conf' and a service configuration as well.
rsyncd.conf:
uid = rsync
gid = rsync
address = example.com
max connections = 10
use chroot = yes
[repo]
path = /pub/share/repo
comment = My Repository
/etc/sysmgr/rsync or what have you:
#!/bin/sh
exec rsync --daemon --no-detach
|
