Starting a site

Does 2.0 support wildcard IPs to listen on all interfaces?

Cheers!

-Boris
(Sent from a BlackBerry)

----- Original Message -----
From: [hidden email] <[hidden email]>
To: The Squeak Enterprise Aubergines Server - general discussion. <[hidden email]>
Sent: Wed Aug 22 07:23:07 2007
Subject: Re: [Seaside] Starting a site

Hi Andrés,

Andres Fortier wrote:
> thanks Janko, it works like a charm. Now, have a doubt: if I try
> accessing the site in the old way (http://localhost:8001/...) it doesn't
> work anymore; is there a way to configure the site (or the server) to
> listen to both the ip and localhost?

Yes, you can add one or more aliasese to the Swazoo Site. And not only
hostname aliases but a whole host:ip:port combination. And that's what
you need to do in your case:

  1. SwazooServer stop
  2. inspect your Site
  3. yourSite addAlias:
        (SiteIdentifier host:'localhost' ip:'127.0.0.1' port: 8001)
  4. SwazooServer start

If you inspect now a SwazooServer singleton servers, you'll now see two
HTTPServers serving on two ip:port combinations but for the same Site!

Best regards
Janko


>
> Thanks again,
>              andreś
>
> Janko Mivšek escribió:
>> Hi Andrés,
>>
>>
>> Andres Fortier wrote:
>>> Hi list,
>>>         First of all I must say that my knowledge in networks is very
>>> limited, so maybe this is well-known in the community.
>>>
>>> I've finally finished my simple site, put it in the server and tested
>>> it via http://localhost:8001/...
>>>
>>> Now, the strange thing is that if I try to access it by using the
>>> server ip (http://xxx.yyy.zzz.www:8001/...) it doesn't work. I've
>>> been told by the guys in tech suport that the server was only hearing
>>> in the localhost interface and that I should set it up to listen in
>>> all the other interfaces. Any ideas how to solve this? I'm using
>>> Seaside with Swazoo on VW.
>>
>> Try to do something like this:
>>
>> 1. SwazooServer stop.
>> 2. Inspect SwazooServer singleton sites and in your site inspect
>>    uriPattern.
>> 3. set host:ip:port: combination accordingly. For instance:
>>     host: 'www.mysite.com'
>>     ip: 'xxx.yyy.zzz.www'
>>     port: 8001
>> 4. if necessary put in hosts file on your computer:
>>     xxx.yyy.zzz.www  www.mysite.com
>>
>>
>> I hope that helps
>>
>> Best regards
>> Janko
>>
>

--
Janko Mivšek
AIDA/Web
Smalltalk Web Application Server
http://www.aidaweb.si
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

The key here is that you configured rails to bind to localhost which is different from 0.0.0.0, Swazoo supports the former but not the latter due to the way it looks up its virtual sites. At this point I suspect I might be better off waiting for Opentalk to take shape on VisualWorks :)

Cheers!

-Boris
(Sent from a BlackBerry)

----- Original Message -----
From: [hidden email] <[hidden email]>
To: Seaside - general discussion <[hidden email]>
Sent: Thu Aug 23 18:03:21 2007
Subject: Re: [Seaside] Starting a site

Hi Boris, this is a very good question.  I have used Ruby and Rails and there's an application called mongrel_rails:

sudo mongrel_rails cluster::configure -e production -p 8000 -N 3 \
-c /var/www/apps/testapp

Note:  The above line configure 3 mongrel instances (i.e. web servers) in production mode starting at port 8000.  Thus, ports 8000 - 8002 would have an instance of the rails webserver running on it.  This would create a file called
mongrel_cluster.yml
.  This looks like the following:
---

port: "8000"

environment: production

address: localhost

pid_file: log/mongrel.pid
servers: 3



Now, that I have generated the cluster file.  I can perform the following actions:

sudo mongrel_rails cluster::start


sudo mongrel_rails cluster::stop


sudo mongrel_rails cluster::restart
Next, I would configure Apache's mod_proxy_balancer by inserting the following lines in my
conf file:



<Proxy balancer://mongrel_cluster>
    BalancerMember http://127.0.0.1:8000
    BalancerMember http://127.0.0.1:8001
    BalancerMember http://127.0.0.1:8002
</Proxy>
Note:  I skipped a few steps but you can get the gist of what's going on in the above.


Finally, it would be great if Swazoo or another application (
i.e. Swazoo-Cluster) allowed one to
configure the relevant pieces of a Swazoo webserver.  Then you can use this Swazoo-Cluster
application to start, stop, and restart the Swazoo webservers for a given application.



-Conrad

On 8/23/07, Boris Popov <[hidden email] <[hidden email]> > wrote:

        Janko,
       
        I do remember having this discussion as well, but in many situations you are deploying behind a web server of some sorts by proxying the Seaside/Swazoo combo, so IP configuration takes place there and does not belong in the application, at least as far as I'm concerned. So I want to bind to all addresses and let other people (or load balancers) decide which ones they will route traffic to (this becomes even more important in managed environments, which is where we are currently moving to).
       
        In a nutshell given the following two choices, which would you prefer if you wanted to listen on all interfaces?
       
        A) Query the host for its interfaces and bind to all of them individually
        B) Bind to 0.0.0.0 <http://0.0.0.0>
       
        Thanks!
       
        -Boris
       
        --
        +1.604.689.0322
        DeepCove Labs Ltd.
        4th floor 595 Howe Street
        Vancouver, Canada V6C 2T5
        http://tinyurl.com/r7uw4
       
        [hidden email]
       
        CONFIDENTIALITY NOTICE
       
        This email is intended only for the persons named in the message
        header. Unless otherwise indicated, it contains information that is
        private and confidential. If you have received it in error, please
        notify the sender and delete the entire message including any
        attachments.
       
        Thank you.
       
        > -----Original Message-----
        > From: [hidden email] [[hidden email]
        > [hidden email] <[hidden email]> .org] On Behalf Of Janko Mivšek
        > Sent: Thursday, August 23, 2007 2:49 PM
        > To: Seaside - general discussion
        > Subject: Re: [Seaside] Starting a site
        >
        > Boris,
        >
        > Boris Popov wrote:
        >
        > > Mostly because I just don't want to query the host to see which IPs
        > > are available when 0.0.0.0 is out there and waiting for me to use it :)
        > > Single site restriction is just fine for ~100% of Seaside users anyway.
        >
        > We already had a debate on that. I think that most users are just happy
        >   with default 'localhost' configuration when they start with Swazoo.
        >
        > Because immediately when you want to go public, you need to register
        > your hostname and ip anyway! Not to mention when you are going to host
        > on some server with many ip's, etc etc. What is missing of course is
        > better documentation how to do that in Swazoo.
        >
        > I think that your case is a special one and I don't understand why
        > should Swazoo be complicated to deal with just your special case?
        >
        > That doesn't mean that we won't introduce that feature in future Swazoo
        > of course.
        >
        > Best regards
        > Janko
        >
        >
        > --
        > Janko Mivšek
        > AIDA/Web
        > Smalltalk Web Application Server
        > http://www.aidaweb.si
        > _______________________________________________
        > Seaside mailing list
        > [hidden email] <[hidden email]> .org
        > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
        _______________________________________________
        Seaside mailing list
        [hidden email] <[hidden email]> .org
        http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside