. It's greatly appreciated!
Joe Goldthwaite
-Original Message-
From: django-users@googlegroups.com [mailto:django-us...@googlegroups.com]
On Behalf Of CLIFFORD ILKAY
Sent: Wednesday, March 04, 2009 3:53 PM
To: django-users@googlegroups.com
Subject: Re: Accessing the development server
Joe Goldthwaite wrote:
> It makes sense that the dev server won't listen to other requests. The
> question is then, how to I explicitly specify which address(es) that I want
> the dev server to listen on?
Just like you did when you typed:
manage.py runserver 0.0.0.0:8000 (listen on port 8000 on
jango-users@googlegroups.com
Subject: Re: Accessing the development server from another machine.
Joe Goldthwaite wrote:
> I don't think it's a network problem. I've got Zope running on port 80 of
> this same VM and can access it from any of the other computers. I thought
> it mig
Joe Goldthwaite wrote:
> Tried it. I no longer get the “getaddrinfo failed” error message. I’m
> now able to access the server as localhost or 127.0.0.1 but no
> 192.168.1.117.
What does the output of "ipconfig" on Windows and whatever the
equivalent is in OS X look like? To which machine is 192.
Joe Goldthwaite wrote:
> I don't think it's a network problem. I've got Zope running on port 80 of
> this same VM and can access it from any of the other computers. I thought
> it might be related to using a different port than 80 so I stopped Zope and
> tried running the development server on 80
re must be a setting somewhere.
_
From: django-users@googlegroups.com [mailto:django-us...@googlegroups.com]
On Behalf Of Karen Tracey
Sent: Wednesday, March 04, 2009 3:00 PM
To: django-users@googlegroups.com
Subject: Re: Accessing the development server from another machine.
On We
:38 AM
To: django-users@googlegroups.com
Subject: Re: Accessing the development server from another machine.
Joe Goldthwaite wrote:
> My main development is done in a Windows virtual machine
> running on a Macbook Pro. Today I wanted to test the output with Safari.
[snip]
> It looks like
On Wed, Mar 4, 2009 at 4:51 PM, Joe Goldthwaite wrote:
>
> Thanks Alex. That did something. Now I'm getting this;
>
> >c:\DjangoProjects\FiscalCalendar>manage.py runserver 0:8000
> >Validating models...
> >0 errors found
> >
> >Django version 1.0.2 final, using settings 'FiscalCalendar.settings'
that I can see.
Stepping through the start up in the debugger makes my head hurt.
-Original Message-
From: django-users@googlegroups.com [mailto:django-us...@googlegroups.com]
On Behalf Of Alex Gaynor
Sent: Wednesday, March 04, 2009 11:44 AM
To: django-users@googlegroups.com
Subject: Re: A
Joe Goldthwaite wrote:
> My main development is done in a Windows virtual machine
> running on a Macbook Pro. Today I wanted to test the output with Safari.
[snip]
> It looks like it's working but when I enter the address in the browser I get
> a connection timeout error. The server never gets the
On 3/4/09, Joe Goldthwaite wrote:
>
> I've been developing with the development server with the default settings
> without problems. My main development is done in a Windows virtual machine
> running on a Macbook Pro. Today I wanted to test the output with Safari.
> Since I don't have that instal
I've been developing with the development server with the default settings
without problems. My main development is done in a Windows virtual machine
running on a Macbook Pro. Today I wanted to test the output with Safari.
Since I don't have that installed in Windows, I decided to just try
connect
12 matches
Mail list logo
