How painful is the deployment of the django project on a live (intermediate) site?

Question

I am developing quite quickly a small django project that I am developing locally, of course. But since I have never worked with django before, I don’t know what it means to download it and test it on a production server. And I'm very curious, as I really want to check out the early release on the air.

I know there is this document that I think will be very useful: http://djangobook.com/en/2.0/chapter12/

But are there any details that I must consider before, during, and after deployment? Any tips or tricks?

Thank.

Answer 1

/ . , , PostgreSQL mod_wsgi SQLite . , , .

Answer 2

, : URL , url.

, .

, , Virtualenv, .

dev , .

Answer 3

- south, - buildout , ( , ), .

Answer 4

I think a lot depends on changing the database model. Django can add new columns using syncdb or generate a script for this, but it won’t remove the columns, and I don’t think it will remove the foreign key constraints from the database even if they are no longer applicable.

Thus, database migration can be best done using scripts and tested on a copy of the production database or some data sets very close to the production data (the same scheme, of course).