On Thu, Jun 16, 2011 at 1:26 PM, DK <cypre...@gmail.com> wrote: > Hi, > > I need to develop several django projects (let's assume that there are > highly different one from each other). The common thing is users/groups > data. If a user register into one of this sites, he should be able to use > this same account credentials for all other sites. >
I'm going to reply based on the assumption that the different sites are kept within multiple code bases? > > I really didn't find any obvious solution to this problem: > > 1) Keeping everything in one database (single django project) - not > possible, every of a project is big enough to be worth keeping separate, > also using something like SITES (not really an issue here) would provide do > keeping data of all separate projects in one big database, what will cause a > problems with maintenance (backuping everything together, etc.). > Not a good idea, you could open yourself up to all sorts of race conditions, compatibility, and migration issues. > > 2) Using django multiple database support - this would be great to put > auth models into seperate common database, but django does > not officially support multidatabase foreign key relations - making this > useless. Any model with relation to auth.User would not be supported this > way (in my projects almost every thing is somehow conneted to the user so > this is dead end for me). > Same as above. > > 3) Using several databases and keeping auth tables in sync by external tool > - very, very error prone. Writing something that deals with coherency > problem will be very difficult, and there also will be a delay between > sync's of databases in several projects - not really acceptable - user data > should be stored in one point. > Noooooooooo. > > 4) Creating central authorization point with Profiles, and make custom > django authorization module that would work exaclty like OpenID > authorization. But this still do not solve problem of NOT having multiple > accounts in several django projects (even connected to one central Profile). > Having a central authorization point is the way forward. I'm a bit confused by this comment though: "But this still do not solve problem of NOT having multiple accounts in several django projects" Could you explain what you mean? Cal > > Any idea? > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-users/-/2m_lo5mn8sYJ. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
