On Sat, 8 Apr 2017, Sithembewena Lloyd Dube wrote:
Do take the time to peruse the book. It would be time well spent. Also, do keep in mind that the recommendations therein do not apply to a Django blog or CRM sustem etc, per se. They would apply just as well if you were building a RESTful mobile app backend.
Sithembewena, I recognized this the first time I considered using django.
The problem you describe of managing users etc is just a requirements specification. The advice in the book is general enough across implementations of solutions in broad problem domains. It's not a recipe book, but more a collection of chefs' knives.
My original question was not about structuring django code but the logical design of the project itself. I believe that question was answered by a message on another thread: there is at least one plug-in package that allows individual users to work in their own database area and keeps users from areas assigned to others. This is independent of the django project/app code arrangement. Thanks again, Rich
