Thanks, Timuçin, your response led me to some interesting education,
but it does not really solve my problem.  I need to set the appliance
to some address; there may be multiple appliances on the same server;
and they will each require their own IP address.  Really what I am
asking is whether there is a way to override the IP address assigned
in development.ini at run time or do I need to edit development.ini
(or production.ini)?  For example, I would really like to be able to
use something like:

paster serve --ip=192.168.97.33 production.ini

in my init.d script.

My appliance needs to be accessible from outside the server on which
it is being run as a virtual machine, but still only within the
firewall (not the public network (that's why I can use the 192.168
kind of private address).
I'm sorry that I was not more clear yesterday.

Thanks,
Herb

On Sep 11, 6:16 am, Timuçin Kızılay <[email protected]> wrote:
> On 11-09-2010 15:46, herb wrote:
>
> > I am building an appliance that includes a TG2.0 application.The
> > appliance user can change the IP address of the appliance, but
> > development.ini specifies the host.  If I use localhost, it cannot be
> > accessed by other machines on my network.  Is there a way to over-ride
> > this IP address when invoking the application with paster or is there
> > a way to make this more dynamic?  Am I stuck with editing the .ini
> > file each time the IP changes?
>
> > Thanks,
> > Herb
>
> I'm using ip address of 0.0.0.0 in development ini. this 0.0.0.0 meand
> listen on all ip addresses on the machine.

-- 
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/turbogears?hl=en.

Reply via email to