Excuse me for giving advice for this change. But why don't you put these two projects in one Django project as two apps? You have two options. First you can make a ManyToMany relationship. Of course this has a problem. For example some people may not want to share his/her future information to a doctor.
There is other way also. You can copy data from one app to another one. Or one model to another. On Monday, January 15, 2018 at 8:12:59 AM UTC+3:30, chern...@gmail.com wrote: > > So i have 2 django project. Both have its seperated database and table. I > create the django rest framework api for both project but i want both of > them to communicate with each other. > > > In django 1 is about the social media and medical record app API. In > django 2 is a clinic app API where the it is for staff of the clinic and > collect user information from django 1 and to give a queue number for user > that make appointment. > > > What im trying to do is django 2 will have a qr code for django 1 to scan. > After scanning, it will ask for permission to allow their information to be > share with django 2(their user information/medical record). After user > allow, their information will be save to django 2 database. > > For now, i just want to allow django 2 to save the user information from > django 1. > > > Is there a way for 2 different django project to communicate with each > other through the api ? > -- 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+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/4137338d-1da2-411b-b300-95ec4c32d439%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
