-
Notifications
You must be signed in to change notification settings - Fork 1
/
howto
29 lines (23 loc) · 1.19 KB
/
howto
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
-how to copy website
# wren to SF (launched on wren)
~kris/bin/rsync --progress --rsh=ssh --exclude=registered/.htaccess -uavCz . [email protected]:stir/htdocs
# SF to wren (launched on wren)
~kris/bin/rsync --progress --exclude=STIRweb1.2.tar.gz --rsh=ssh --exclude=registered/.htaccess -uaCzv [email protected]:stir/htdocs/ .
# PC to wren
rsync --rsync-path=~kris/bin/rsync -auCzv --exclude=registered/.htaccess ./ web@wren:htdocs/STIR/
# wren to PC
rsync --rsync-path=~kris/bin/rsync -auCzv --exclude=registered/.htaccess web@wren:htdocs/STIR/ ./
# PC to SF
rsync -auCzv --exclude=registered/.htaccess ./ [email protected]:stir/htdocs/
# SF to PC
rsync -auCzv --exclude=registered/.htaccess [email protected]:stir/htdocs/ ./
all files have relative locations, so can be copied freely.
The only exception is registered/.htaccess. This requires in
its content an absolute path to pass/.htpasswd.
At present, I have made copies
.htaccessHI (for Hammersmith Imanet)
.htaccessSF (for the Sourceforge site)
which can be use when .htaccess is overwritten. Note that their
permissions are more restrictive than for .htacess, so if you
copy them, adjust permissions with
chmod go+r .htaccess