Files
kennethreitz.org/data/essays/2009-01-django_remote_development_server.md
2025-08-27 08:08:17 -04:00

21 lines
1.4 KiB
Markdown

# Django Remote Development Server
*January 2009*
![](http://media.kennethreitz.com/images/django-logo.png) If you've worked with Django much at all, I'm sure you've had this problem: wanting to access the built\-in development webserver remotely<label for="sn-1" class="margin-toggle sidenote-number"></label>
<input type="checkbox" id="sn-1" class="margin-toggle"/>
<span class="sidenote">This simple technical tip reflects the distributed development practices emerging in 2009—before cloud development environments like Codespaces, developers were pioneering remote development workflows that would become standard practice.</span>. Typically, this integrated mini\-server ignores all requests from any IP Address other than 127\.0\.0\.1 . If you run the following command, however, it will be accessible remotely. VERY useful for remote dev work.
```
manage.py runserver 0.0.0.0:8000
```
Enjoy<label for="sn-2" class="margin-toggle sidenote-number"></label>
<input type="checkbox" id="sn-2" class="margin-toggle"/>
<span class="sidenote">Kenneth's characteristic brevity and enthusiasm ("Enjoy!") became a signature of his technical writing—providing maximum value with minimal fuss, a philosophy that would define his approach to library design and developer experience.</span>!
[Development](http://technorati.com/tag/Development), [Django](http://technorati.com/tag/Django), [Python](http://technorati.com/tag/Python)