Comments on: Installing and Configuring Django Web Framework with Virtual Environments in CentOS/Debian – Part 1

By: JF

JF — Thu, 05 May 2016 10:55:58 +0000

Here is a video How to install pip, virtualenv, django on Centos 7-- Django tutorial series lecture 1 that will help you much more than others because it's so clear to understand.

By: Gabriel Cánepa

Gabriel Cánepa — Fri, 18 Dec 2015 13:32:34 +0000

In reply to Jochen.

Please see my response to Gavin below.

By: Gabriel Cánepa

Gabriel Cánepa — Fri, 18 Dec 2015 13:32:06 +0000

In reply to Gavin S.

@Gavin,
Thanks for your comment. Let me explain.
1) This series is meant as an introduction to Django (as I explain at the top), and not as a full guide covering security. However, since security is also a concern, we may consider adding an extra article to this series covering that topic for a development environment such as the one described here.
2) When I say “In any event, you can change the default port where the built-in web server will be listening. By using 0.0.0.0 as the network interface to listen on, we allow other computers in the same network to access the project user interface (if you use 127.0.0.1 instead, you will only be able to access the UI from localhost).”, I mean that if you are installing Django in a CLI-only server, how are you supposed to check whether the applications are working (and looking properly) except you can connect to the server from a desktop PC somewhere in the network?
3) You’re absolutely right about the link in the first part of the article. I am asking Ravi, the owner of the site, to take a look and fix it.
Best regards.

By: Jochen

Jochen — Fri, 18 Dec 2015 13:01:56 +0000

What’s the point in running the development server on 0.0.0.0? A) there is no need for that and B) it’s an unnecessary safety concern.

By: Gavin S

Gavin S — Thu, 17 Dec 2015 00:39:18 +0000

This article does not cover the topic well and includes unnecessary information and steps that open security vulnerabilities. Do not open ports on your firewall for “others on the same network” to see your django project unless you know what you’re doing. For most development setups of django localhost is the right way to go. The article says you need virtualenvwrapper then doesn’t make use of it.
On an admin note the whole first part of the article is mistakenly (or just irritatingly) a link.