[Seaside] Re: Deploying Seaside on a Swazoo Server
pat.mcdonald at mail.com
Tue Jun 7 20:12:12 UTC 2011
That's exactly what I'm doing.
preferenceAt: #serverHostname put: 'my.domain1.com';
preferenceAt: #serverPath put: '/'.
and the same for my other domain.
Now when I inspect my WASwazooAdaptor I only have one WAPluggableSite where I would suspect to have two or am I wrong here ?
Should I register my application in a different way ?
----- Original Message -----
From: Paul DeBruicker
Sent: 06/07/11 09:58 PM
To: seaside at lists.squeakfoundation.org
Subject: [Seaside] Re: Deploying Seaside on a Swazoo Server
> In reply to this post by 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 Does setting the #serverHostname preference for each application. e.g. For mydomain1 add this to your initialize method: application preferenceAt: #serverHostname put: 'my.mydomain1.com'. And for mydomain2 add this to your initialize method: application preferenceAt: #serverHostname put: 'my.mydomain2.com'. fix your issue? I've never tried what your doing, so am just guessing. Paul _______________________________________________ seaside mailing list seaside at lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside