Re: [TWiki-Dev] Twiki-sicki?

[Michael S. <ms...@in...>]

On Mon, 28 May 2001, Nicholas Lee wrote:
> On Sun, May 27, 2001 at 04:14:30PM -0700, David Weller wrote:
> > I've noticed it's been sick since Friday... I first noticed it when I was doing
> > a demo for some corporate folks at a major mobile phone company, showing off
> > how well it worked... uh, boy, did I look stupid. :-(
> 
> Sorry about that.
> 
> Support request for sourceforge is listed at:
> http://sourceforge.net/tracker/?func=detail&atid=200001&aid=427346&group_id=1
> 
> 
> I'm sure Peter is working hard on fixing things at the moment.  
> 
> Might be worth mention your event to the admins at sourceforge.  They
> might get the idea that its good to fixes these things quicker.
> 
> 
> It also might be worth us considering a mirror site.  Of course
> ClutsterWiki is no where even design stage. ;)

Not entirely true - I'm in the process of implementing one based on the
various comments I've made in the past. Essentially it boils down to
separating twiki out so that the data and code is separated sensibly -
ie everything to do with a web is in one place, and all the static
code is in one place - and then having one site in the organisation
being the "code reference point" with the code shared using rsync, and
the data being shared as follows:

   * Have a central CVS repository as the shared, non-editable directly
     repository.

   * Nightly each Twiki does a CVS sync of it's contents with the CVS
     repository. If there's a clash, then it's a "first win" if possible
     scenario - and the local twiki informs the local user that their
     edits would clash, and the local user has to update their local copy,
     and can request an early sync of their page.

The nice thing about this is that the local twiki keeps the usual read/
write semantics, and if updates with the central CVS can't happen for any
reason,  things keep working. So far we're still in early stages and don't
have this in place, but it doesn't clash with the existing codebase in
style, and should be a relatively simple "bolton".


My personal twiki has grown from a personal one to allow me to go on
holiday without getting questions to one, that is being used by a largish
number of others in our group, and now a world-wide one for internal usage
is being planned(*), but one key thing we're planning for several reasons from
stage one is a Cluster/Distributed Wiki, simply because our setups will
_need_ this, rather than be optional. Having just one site write and the
rest isn't tenable in the long term. In the short term, it's OK, and we can
use rsync for the sync'ing of data as well, but we've currently separated
things out so that data, code & configuration are all separate since these
will/are different at different sites.

    (*) Internal viral .sig advertising style kinda helps here. :-)

Obviously, since Twiki is GPL'd, when this is done, I'll roll it back
in/make it available to the main codebase :-)


Michael.
--------( Michael Sparks, I N K T O M I - UK Technical Support )-------
    Land: +4420 7430 5807 Page: +447641 104 011 Mob: +447775 903 268
      Email: ms...@in...  http://websupport.inktomi.com/