On 19-Mar-2002, Hicks, Jamey wrote:
>I think it would be a good idea to support mirrors of handhelds.org.
How about a mirrors.html document, reachable from the home page, that
provides mirroring guidelines?
To avoid having to explain a bunch of special cases, and to support
mirroring easily as future projects are added, it would help to have a
consistent policy on how project downloads are organized. Perhaps
something like this:
1. Each project <foo> gets a dedicated download subdirectory in some
top-level directory, say /home/downloads/<foo>.
2. The following URLs point to /home/downloads/<foo>:
ftp://ftp.handhelds.org/downloads/<foo>
http://handhelds.org/downloads/<foo>
rsync://handhelds.org/downloads/<foo>
3. Additionally, each project <foo> with a <foo>.handhelds.org domain
gets URLS pointing to /home/downloads/<foo>:
ftp://ftp.handhelds.org/<foo>
http://<foo>.handhelds.org/downloads
Then, mirrors.html could be as simple as:
We welcome mirrors of the public download areas on handhelds.org.
To conserve bandwidth, please use rsync to update your mirror. rsync is
available from http://rsync.samba.org/.
Each project's download area is a subdirectory of
rsync://handhelds.org/downloads, so to mirror project "foo", you could
run something like this:
rsync -vaz rsync://handhelds.org/downloads/foo /mirror/handhelds/foo
If you only want to mirror a portion of a project, for example its
unstable feed, you can specify the files or subdirectories you want on
the rsync command line:
rsync -vaz rsync://handhelds.org/downloads/foo/feeds/unstable .
You can browse the rsync download area by visiting
http://handhelds.org/downloads or ftp://ftp.handhelds.org/downloads.
What do you think?
To implement this, I'd use symlinks to avoid breakage of existing paths.
Nick
Received on Fri Mar 22 20:10:25 2002
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:42:40 EDT