[Seaside] deploying a 3.0 app

[Sean Allen]

I apparently wasnt very clear.

Seaside 2.8 had a deployment mode to turn off halos, etc, lock the
seaside installation down.
Seaside 3 seems to have broken this off into different parts and we
are about to deploy a
Seaside 3 application w/o feeling particular good about our understand
of what needs to
be done to lock the application down.

Is there an faq entry for Seaside 3 that address the 'this is what you
should do to lock your
application down when deploying' questions? Or a blog post or two...


On Thu, Jan 7, 2010 at 1:49 AM, Lukas Renggli <renggli at gmail.com> wrote:
> The [Seaside Book][1] has a chapter on [deployment][2]. It describes
> how I typically deploy a Seaside application.
>
>  [1]: http://book.seaside.st/book/
>  [2]: http://book.seaside.st/book/advanced/deployment/deployment-apache
>
> 2010/1/7 Sean Allen <sean at monkeysnatchbanana.com>:
>> Is there a good faq listing anywhere of all the changes in settings
>> you should make when deploying a 3.0 application?
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>
>
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>