[Seaside] Deploying Seaside on a Swazoo Server

[Pat McDonald]

Hi Nick,

 Sorry but I don't get it :(. 

 Let me explain a bit more. I have 2 small "private use" sites. I want to access them with their own domainname and that doesn't work.

 I can access them with my.domain1.com/domain1 and my.domain1.com/domain2 or my.domain2.com/domain1 and my.domain2.com/domain2, but using my.domain1.com or my.domain2.com just gets me the Welcome screen. I guess I must change the default of WADispatcher, but do I need to do this for both sites ? 

 Pat

----- Original Message -----
From: Nick Ager
Sent: 06/03/11 10:58 AM
To: Seaside - general discussion
Subject: Re: [Seaside] Deploying Seaside on a Swazoo Server

 Hi Pat,
Right, I don't want people to have to type the extra /mysite. The book doesn't really help as I'm only using Swazoo as server and I don't have an Apache at the moment. Maybe I will in the future.

 at the bottom of the link I posted (http://book.seaside.st/book/advanced/deployment/deployment-preparing ) is a solution to removing extra /mysite (even using the Swazoo):

preferenceAt:#serverPathput:'/

 I've also written about it on my blog: http://nickager.com/blog/serving-seaside-requests-without-the-application-name-in-the-URL/ 

 HTH

 Nick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20110607/53b884a5/attachment.htm