[Seaside] Re: seasidehosting.st - questions, comments, tips

Yanni Chiu yanni at rogers.com
Mon Mar 6 16:11:08 UTC 2006

I just deployed an update, and re-read this posting,
so I thought I'd fix some things.

> I had to upgrade Seaside from 2.5 to 2.6. It was a simple
> connect to SqueakSource, find the latest 2.6, and load.
> I upgraded ShoreComponents as well, and chose the 2.6 version.
> Then I had to downgrade to the latest 2.5 version, because
> the 2.6 version used the canvas API by default. Luckily,
> the latest 2.5 version works, as far as I've tested.

I wrote this badly, and caused some confusion. I had to
downgrade to ShoreComponents-2.5, not Seaside-2.5.
My app doesn't use the canvas API of Seaside-2.6 and
ShoreComponents-2.6. Luckily, ShoreComponents-2.5 was
compatible with Seaside-2.6.

> Here's my deployment procedure:
> - sanity check of app
> - use the config app to remove all entry points other
>   than config and my apps
 > ...

While in the config. app:

- Set "default entry point:" (2.6 only) to the your main app
   (Otherwise, if your image is restarted, you'll have to do
   it online, after each restart).

More information about the Seaside mailing list