[Seaside] Re: [squeak-dev] Upgrading running servers?

Ken Causey ken at kencausey.com
Wed Apr 2 16:59:43 UTC 2008

Well, I can only say that I've updated (without restarting) a handful of
images that were running either Seaside or something else using Kom and
have not had any troubles.  In most cases these were images that were
probably not getting but a few hits a minute, but I believe in at least
one case we made changes to Swiki (yes, wiki.squeak.org) and had no
trouble.  Those were very minor changes though if I remember correctly
(just a method or two).


On Wed, 2008-04-02 at 09:28 -0700, Andreas Raab wrote:
> Hi -
> [Apologies for the cross-post but there may be answers to this question 
> coming from people who are subscribed to Seaside but not Squeak-dev]
> What are the best practices for upgrading portions of your running 
> server? I'm not talking about replacing the main business logic of your 
> server application but rather relatively small things like an improved 
> log module, or an administrative report function etc. Basically parts 
> that you can assume aren't used while you upgrade them.
> I was quite surprised that I wasn't able to find any recommendations on 
> how to do that. And I can't imagine that this problem hasn't come up in 
> Seaside or other Squeak or Smalltalk server deployments. So what do 
> people do in such a situation? Fire up VNC and load the latest MC 
> package? Is that feasible when you have hundreds of users pounding the 
> server? Any other (semi- or fully-) automated variants? Alternative 
> recommendations?
> Thanks for any insights you can share.
> Cheers,
>    - Andreas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.squeakfoundation.org/pipermail/seaside/attachments/20080402/63c45e4a/attachment.pgp

More information about the seaside mailing list