Am 04.04.2004 um 16:22 schrieb goran.krampe at bluefish.se:

> Bert Freudenberg <bert at impara.de> wrote:
> [SNIP]
>>> We should probably look into getting a backup SM server going
>>> somewhere, since SM is now accessed by the update stream.  The update
>>> stream has two servers (SqF and gsug.org), so SM probably should have
>>> backup as well...
>>
>> Just give me an FTP accessible directory for all SM packages so that I
>> can set up a mirror for them at GSUG. When loading a package, the
>> system knows the full URL, right? So mirroring only the packages 
>> should
>> work, provided the SM loader looks in the backup location, too.
>>
>> Additionally, a notification email would be nice to get whenever a new
>> package version was added (to keep the mirror latency low).
>
> Hmm. I think this would be the "best" way to set up a working mirror:
>
> 1. Set up a slave map that has no login (readonly web UI) and that does
> "loadUpdates" once per 10 minutes or whatever. If there are no new
> changes it is just a very small HTTP GET request. If the slave server 
> is
> a Debian machine I already have init.d scripts etc.
>
> 2. Use rsync to synch the file areas on the master server to the slave.
>
> We can then set up how many of these readonly mirrors as we like. If
> this sounds good I can get the needed changes for this to work (the
> package download mechanism must be tweaked to be able to test multiple
> locations etc) and write down a small howto for it ASAP.

There is no Squeak running on the gsug.org machine, just Apache. I can 
only offer to mirror package files,

How complicated is it to fetch a package from SM? Is the SM loader not 
just downloading a single file, referenced by its UUID? If not, maybe 
we should arrange that it does.

- Bert -