Hi All, Another option which no one mentioned yet would be to keep all of the code for _both_ projects in the same repo and share common code that way.
Collin On Tuesday, December 23, 2014 12:22:03 PM UTC-6, andy wrote: > > Hi, > > I have two Django Projects that have different use cases. There are > reached using different domains. They are hosted in two different servers. > Also each Django project has it's own database. > > Now, both the projects have some models and some business logic common > between them. I don't want to duplicate the code and data which shall be > chaotic going forward. Also, I want the models and code (business logic) to > be in sync (when models/code is altered). > > Can anyone guide me towards a pattern that can help me attain the required > architecture: 2 separate projects with common models and business logic. > > Thanks in advance. > > /andy > > P.S. This is my first post. So pardon me for breaking any forum etiquette. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/f9805037-b7a0-4f7a-8f3a-46e94aec8a44%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
