How to structure this django application

36 views
Skip to first unread message

Rich Shepard

unread,
Apr 7, 2017, 6:54:11 PM4/7/17
to django...@googlegroups.com
Caveat: I'm not a professional coder or web developer, but have written
many applications over the years. Because I'm also new to django I need
insights into how to structure an application application supporting
multiple users, each in its own private section.

This application will allow my clients to upload data to the web site,
each in his own space. Data will be stored in a postgres-9.6+ backend.
Generated reports will be available for download.

I understand that a django application has many 'apps' in it and is not a
single-file framework. If there is an example of how to set up and structure
such an application please point me to it so I can learn from success.

Pointers, references to docs or web sites will be appreciated and used.

TIA,

Rich

Sithembewena Lloyd Dube

unread,
Apr 7, 2017, 7:04:43 PM4/7/17
to django...@googlegroups.com
Hey Rich, 

My best recommendation for structuring Django projects (and for optimization and a myriad other goodies) would be the book Two Scoops of Django by Daniel and Audrey Roy Greenfeld. I could say a lot but the bottom line is, check the book out. It's at https://www.twoscoopspress.com/

There are various factors to consider and this book (to me, at least) best encapsulates all those. I believe that it also applies for newer versions of Django than v1.8.

Best regards, 
Sithembewena 

Rich Shepard

unread,
Apr 7, 2017, 7:35:14 PM4/7/17
to django...@googlegroups.com
On Sat, 8 Apr 2017, Sithembewena Lloyd Dube wrote:

> My best recommendation for structuring Django projects (and for
> optimization and a myriad other goodies) would be the book Two Scoops of
> Django by Daniel and Audrey Roy Greenfeld. I could say a lot but the bottom
> line is, check the book out. It's at https://www.twoscoopspress.com/

Sithembewena,

I have that book (the 1.8 version); pulled it off the shelf earlier today
to read again.

> There are various factors to consider and this book (to me, at least) best
> encapsulates all those. I believe that it also applies for newer versions
> of Django than v1.8.

What I need to build is different from a blog, newspaper, e-commerce, and
similar sites ... I think. In those, every visitor/user sees the same views
and has the same options.

My proposed application needs to be slightly different for each category
of user and keep each in his/her own private section. How to do this may be
in 2 scoops, or may not. If I don't see how to do this I'll be back with
more questions.

Thanks,

Rich

Sithembewena Lloyd Dube

unread,
Apr 7, 2017, 11:45:28 PM4/7/17
to django...@googlegroups.com
Hey Rich, 

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.

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. 

Best regards, 
Sithembewena 

On Apr 8, 2017 01:34, "Rich Shepard" <rshe...@appl-ecosys.com> wrote:

Rich Shepard

unread,
Apr 8, 2017, 8:49:05 AM4/8/17
to django...@googlegroups.com
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
Reply all
Reply to author
Forward
0 new messages