3👍
In such cases, I think, it makes sense to make some kind of internal interface through which your sites would communicate, and expose only one of them to public. That would make everything more maintainable.
For example, your friend can make his PHP pages to output information in JSON or YAML. In corresponding Django views, you’ll have little to no logic, just making internal HTTP requests to these pages, and basically passing the data to templates.
This way, you’ll have output via Django templates, and some logic still in PHP. If PHP code does some work with database or performs computation that can’t be converted easily enough to Python, and you have limited time, this option may be the best.
Though, I guess, it depends a lot on the architecture of the project, especially the PHP part. There’s not enough information to say what’s the best option for you.
1👍
Don’t mix languages if you have any other option. Honestly, I don’t think the type of integration you’re imagining is even possible. About the closest you would ever get would be two separate websites that shared a common look and feel and passed info back and forth to each other. At the end of the day, though, there would always be a separation of management and data.
There’s some pretty robust PHP frameworks out there. Assuming your friend is using one of those, you’ll need to decide which best fits with the time and skills you both have to devote to the project. If your friend is not using a framework, the decision is simple: move everything over to Django.
- [Django]-Django parler create test objects
- [Django]-Django how to open file in FileField
- [Django]-Django JSONField filtering Queryset where filter value is annotated sum value
- [Django]-Django authentication in django nonrel on GAE
- [Django]-Model_to_dict is not returning DateTimeField with auto_now_add = True