On 28/10/2016 5:17 PM, Deep Shah wrote:
> I have read this, but still confused. What would be the best practices
> for this?
Your email doesn't say what you have read ("this" above?) so the
following recommendation may be a duplication. In any case I recommend
Two Scoops of Django[1] for well reasoned strategies for project design.
The authors use as their example an Ice Creamery and among the
sub-applications they design is a loyalty program. I would gues it won't
be too far away from your project.
[1]
https://www.twoscoopspress.com/products/two-scoops-of-django-1-8
>
>
> On Wednesday, October 26, 2016 at 12:05:19 PM UTC+5:30, Deep Shah wrote:
>
> I have a django project which is a loyalty program for
> restaurants. The different database tables are- Users (and
> extending it with User Profiles), Restaurant Company (the entire
> chain), Branches, Offers, Points (points which users get on
> visiting a particular restaurant) etc.
>
> How do I structure my project? Which of these would be my apps,
> and which model would come under which app?
>
> --
> You received this message because you are subscribed to the Google
> Groups "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
django-users...@googlegroups.com
> <mailto:
django-users...@googlegroups.com>.
> <mailto:
django...@googlegroups.com>.
>
https://groups.google.com/d/msgid/django-users/c76e9350-a25d-40b4-8d83-bf9b689cda6a%40googlegroups.com
> <
https://groups.google.com/d/msgid/django-users/c76e9350-a25d-40b4-8d83-bf9b689cda6a%40googlegroups.com?utm_medium=email&utm_source=footer>.