[Seaside] About Seaside 3.0

Ramon Leon ramon.leon at allresnet.com
Sun Jul 13 02:24:30 UTC 2008

> Philippe,
> Why?  That then forces users to set up Apache, and then configure it
> correctly.  Squeak/Pharo should be able to do SSL on its own, and can
> thanks to the cryptography group's efforts.  With some extra 
> effort, it
> could serve secure pages on its own.  Just about any otherwise
> non-Seaside service could benefit from such a simple to manage secure
> web server.
> Bill

Bill, a simple question, why do so many Smalltalker's insist on reinventing
the wheel?  Apache isn't just a web server, it's *the* platform of the
Internet and it's not some trivial thing to simply reimplement and replace
everything it can do for you out of the box.  Isn't it about time to learn
how to play nice with the outside world and stop insisting that every single
piece of the tool chain be implemented in Smalltalk?  

Despite what you're implying, Apache is not that difficult to setup and
there's tons and tons stuff available for making it do anything you want.
As for setting it up with Seaside, you could easily find a dozen different
working configurations prewritten with a trivial look through the Seaside
forums.  Yes, that stuff should be easier to find, possibly posted on the
seaside.st site in a visible place.  With a prewritten config, setting up
Apache probably takes less time than installing Seaside.  This is all it

<VirtualHost *:80>
    ServerName yoursite.com
    DocumentRoot /var/www/yoursite.com
    RewriteEngine On
    ProxyRequests Off
    ProxyPreserveHost On
    UseCanonicalName Off
    RewriteRule ^/seaside/files(.*)$ http://localhost:3001/seaside/files$1
    RewriteRule ^/(.*)$ http://localhost:3001/seaside/yoursite/$1 [P,L]

Is it really worth all that effort to avoid this tiny little config file and
avoiding using one of the most solid, stable, and powerful tools available
to you?

Ramon Leon

More information about the seaside mailing list