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' >Development server is running at http://0:8000/ >Quit the server with CTRL-BREAK. >Error: (11001, 'getaddrinfo failed')
I tried stepping through everything in my IDE (Komodo IDE 5.0) but I don't get that error message. I actually don't get anything. It just runs and stops without outputting anything 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: Accessing the development server from another machine. On 3/4/09, Joe Goldthwaite <j...@goldthwaites.com> 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 installed in Windows, I decided to just try > connecting with Safari from OSX to the virtual machine. That led me to an > adventure into the runserver settings. > > It looks like I should be able to just enter "manage.py runserver > 192.168.1.117:8000" to expose the development server to the network. When I > try it, it looks like it's working and I get this; > >>c:\DjangoProjects\FiscalCalendar>manage.py runserver 192.168.1.117:8000 >>Validating models... >>0 errors found >> >>Django version 1.0.2 final, using settings 'FiscalCalendar.settings' >>Development server is running at http://192.168.1.117:8000/ >>Quit the server with CTRL-BREAK. > > 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 request. I'm not > running any firewall. Is there some other setting somewhere that allows the > development server to serve up requests to external browsers? > > > > > Try running the server at 0:8000 this tells it to serve requests to all hosts. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." --Voltaire "The people's good is the highest law."--Cicero --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
