M
M
mx60012015-06-22 21:59:21
Django
mx6001, 2015-06-22 21:59:21

Should I use Django's built-in server when developing?

I am doing my first Django project which will then go into production. The bottom line is that I work in an organization and I have to develop on Windows, i.e. You can't install another OS. The production server will be CentOS, Django will work on it via apache + mod_wsgi (already configured). But the fact is that it is very dreary to deploy a bundle with django + apache + mod_wsgi on Windows. Since I used to work with PHP and working with it, I was convinced that it is better to have the same configuration (server) on my dev. machine and on the combat server. From this, I had a question whether it is possible to completely build an application on my own using only the built-in Django server and then publish it to the server where apache + mod_wsgi will already be used, is there a big difference between the concept of working Django itself through the built-in server and mod_wsgi? Will I get surprises later in terms of the need to rewrite part of the python code itself under mod_wsgi?

Answer the question

In order to leave comments, you need to log in

2 answer(s)
S
sim3x, 2015-06-22
@mx6001

apache+mod_wsgi
-> nginx+uWSGI
is there a big difference between the concept of working Django itself through the built-in server and mod_wsgi?
concepts are very different.
Will I get surprises later in terms of the need to rewrite part of the python code itself under mod_wsgi?
no, if you don’t screw up
yourself, vagrant will help you test in conditions close to the server

G
GavriKos, 2015-06-22
@GavriKos

You can get. So put yourself a virtual machine, and check in it periodically. Or, in general, develop completely in a virtual environment, if resources allow.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question