On Tue, 2007-08-28 at 10:55 -0500, Adrian Holovaty wrote:
> On 8/28/07, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
> > Here's a suggestion to pull the options out of
> > django.core.management.ManagementUtility: What if we just read the
> > command after manage.py/django-admin.py and then passed the
On 8/28/07, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
> Here's a suggestion to pull the options out of
> django.core.management.ManagementUtility: What if we just read the
> command after manage.py/django-admin.py and then passed the rest of the
> parsing to a separate execute method for each Comman
Oops! Just saw that you were talking about 'testserver' and not
'runserver.' Sorry about that :D
Clint
On 8/28/07, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
>
> The testserver command doesn't currently allow you to set the port for
> the server to run on. I teach high school in a Linux thin clien
Am I missing something here? You can specify the port in the standard
way like this:
./manage.py runserver 0.0.0.0:12345
or
./manage.py runserver 192.168.2.29:45001
Is this not working for you? It's all documented right here:
http://www.djangoproject.com/documentation/django-admin/#runserver
The testserver command doesn't currently allow you to set the port for
the server to run on. I teach high school in a Linux thin client lab, so
all of my students are running on the same server and each needs his/her
own port, unfortunately. (Interestingly, having 10-15 Django dev servers
running
