Back-ends for Monticello?

Philippe Marschall philippe.marschall at gmail.com
Sat Apr 7 18:21:38 UTC 2007


2007/4/7, brad fowlow <fowlow at pacbell.net>:
> Howdy...
>
> Looking for recent experiences/opinions.
>
> We're using Monticello for a lot of source that gets a fair bit of
> update
> (maybe a dozen checkins a day,
> into a set of maybe 50 packages in 5 or 6 repositories.)
>
> We've been using squeak source as the backend, on a Linux box.
>
> Every few days, the 'lost it, spin out of control at 99% CPU' problem
> strikes
> the source server, and someone has to ssh to it, kick it over,
> and then e-mail everyone to check that their recent checkins made,
> reminding the recalcitrant to 'Flush Cache Versions', and so on.
>
> This causes some of the grumpy gray-bearded men
> to become exceedingly grumpy indeed.
> Especially upsetting to the old guard is the unfortunate fact that
> you may not find out right away that your checkin has gone astray.
> (It's only the next refresh in Monticello, not the checkin itself, that
> reveals the situation to the user.)
>
> Sneering has been seen.
> Unfavorable comparisons with SVN have been heard.
> Projects based on languages whose names contain J, or even C,
> have been recalled fondly.
>
> So... we're looking for a more reliable back end.
> The alternatives seem to be FTP and WebDav.
>
> Anyone have experience/advice/guidance about using
> either an ftpd, or some WebDav enablement in an Apache on Linux,
> as the server for a Monticello package repository?

WebDav (actually HTTP, but anyway) + Apache + Linux
no problems at all

If you want to get fancy you can even use SSL via cUrl but this not
seen that much testing but it doesn't use HTTPSocket.

Philippe

> Thanks!
>
> -brad
>
>
>



More information about the Squeak-dev mailing list