Re: [Help-smalltalk] Seaside, some questions...

[Paolo Bonzini]

> - How do you secure the config-site of seaside with - at minimum - a 
> user/password? (I tried a load into squeak, and it asked me for a 
> user/password combination, but where is it saved, that I could set it in 
> gst "by hand"? Or is it because of the difference between swazoo and 
> comanche. And if so, how do you workaround it.)

It looks like this part is unimplemented in Swazoo, OTOH it seems pretty 
easy to do (the HTTPAuthenticationChallenge class is missing).  (swazoo 
list CCed).

I think what is often done, is to firewall Swazoo, and instead use 
Apache as a proxy server.  You then configure Apache to block 
/seaside/config and to use it, you access Swazoo directly (because of 
the firewall, that would be possible only within some kind of DMZ).

> - Do you hide the /seaside/ path somehow for the user?

If you want this, you have to make the root entry point the 
WAApplication instead of using a WADispatcher as Seaside does by default.

> - Do you really need the halos for development? (And if so, how do you 
> activate them. I know the entry about seaside on 
> http://smalltalk.gnu.org, but I couldn't add something like 
> WAToolConfiguration to the configuration of my application. My page 
> looked like: http://up.picr.de/2368288.jpg

click Override in decoration classes. They are not necessary, but very 
useful.

Paolo