2👍
Django organizes code into ‘apps’, which is why you have separate models.py files, and I don’t think there’s a way to put them all in one directory instead, since each app gets its own Python package.
However, the way I normally structure my code, is to have one (or a few, if it’s a larger project) app for all my code, since you can have as many Models in a single models.py file as you want.
I don’t think South will help you with that, but it will make it a lot easier to manage your migrations, so I would highly recommend it.
2👍
I dont think there is a provision in django to put all models at one place. and also it is bad idea to put all at one place. because each app has its own DB Schema and putting apps independent is necessary to fulfill reusability factor. Its better to keep the models isolated from each other, attached to their app as it helps reausability.
South does not fulfill this. it just keeps track of ur Db migrations n fixtures.
At one point or the other, South comes into picture, no matter how perfectly the DB Schema is designed.
- [Django]-Serving static and media files on a distant server with Django and Nginx
- [Django]-Difference Between Satchmo's local_settings.py and settings.py
- [Django]-What is the difference between <int:pk> and <pk>?
- [Django]-Unable to connect to server when running docker django container