You will have to connect one django project to the database as a legacy db.
You'll fake migrate, so django doesn't create it's default models twice. On Wed, 17 Jun 2020, 12:24 am J.T., <[email protected]> wrote: > I have Django project A on one server & Django project B on a different > server. I want project B to be able to load data into the db associated > with project A. > > My question is: do I have to have the app and models on project B exactly > match the app and models on project A? > > Also, other than pointing the settings.py of project B to project A's > database, is there anything else I need to do? > > I do realize this is type of setup is frowned upon, but I need this setup > for at least the time being. > > Thank you. > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/6b565ce5-19f5-485b-9361-48a2f08a6a27o%40googlegroups.com > . > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CADZv-jAfEj-zJXE5K%2BfHLfvhC2dy8BcfFhHFnZExT9ASsBQ%2BDw%40mail.gmail.com.
