[Seaside] Which image for deployment?
johan at inceptive.be
Mon May 30 06:26:45 UTC 2011
imho, the best option is to take a Pharo core image and load only those parts that you need.
Once you have a metacello configuration for your app that loads upstream projects automatically, it's a breeze.
I haven't seen good tools to strip an image though (like the runtime packager of VW). So I'm also interested to hear if anybody does that.
Securing the image: make sure all request handlers (for the installed seaside apps) are removed from the image and add the auth_configuration to those applications you want to keep.
Am I forgetting something?
On 30 May 2011, at 07:50, Davorin Rusevljan wrote:
> I would also like to hear what others think, but there is also one more option: pier image built by jenkins.lukas-renggli.ch
> Davorin Rusevljan
>> On May 29, 2011 11:32 PM, "Sean P. DeNigris" <sean at clipperadams.com> wrote:
>> What is the preferred Pharo image for production deployment? I've seen quite
>> a few options:
>> * stripping a Seaside image from the seaside site
>> * loading Seaside via Metacello into Pharo (although I got an error in Pharo
>> * the Pharo + Seaside image on the Pharo hudson server
>> Also, where can I read about how to strip and secure an image for
>> deployment? I know I've seen info on the lists, but couldn't find anything
>> in Pharo By Example, the Seaside book, or Pharo's CollaborActive book.
>> View this message in context: http://forum.world.st/Which-image-for-deployment-tp3559528p3559528.html
>> Sent from the Seaside General mailing list archive at Nabble.com.
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside