Re: Two Django projects with common models and business logic

If you use Git as VCS: Use submodules. Submodules allow foreign repositories to be embedded within a dedicated subdirectory of the source tree, always pointed at a particular commit. Quote from the link:

It often happens that while working on one project, you need to use another project from within it. Perhaps it's a library that a third party developed or that you're developing separately and using in multiple parent projects. A common issue arises in these scenarios: you want to be able to treat the two projects as separate yet still be able to use one from within the other.

Am Mittwoch, 24. Dezember 2014 17:26:22 UTC+1 schrieb Javier Guerra:

On Wed, Dec 24, 2014 at 11:18 AM, andy <andy...@gmail.com> wrote:
> Thank you. Since it's only me that'd be using the apps do can I bypass the
> 'deploy using pip' thing and somehow directly use it in my other projects?


you could just set links or add to your `sys.path` list, but that
makes it hard not to break one project when developing the other.

a little better is to use your version control system, so now you have
(at least) three projects: project A, project B and a common app, each
on a different repository.  each server would checkout not only the
project-specific code but also the common app

--
Javier

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/76c8a411-840c-43a4-a45d-551bf984e11c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.