linking the brauerei to the ilaris-online api or share the db would provide possibility for some nice features. Keeping the project seperated however would be good to keep the project alive independently even when ilaris-online is not online anymore. So I think the api calls and snippet code should be seperated in a way, that it's easy to remove and/or can be configured to use optionally. Hardcode it everywhere, like the google login was can become anoying. To have some time to test and implement it I put it on milestone for v1 and it could be shifted even further. This issue is to discuss the general approach, where individual related features can be linked:
Your idea:
linking the brauerei to the ilaris-online api or share the db would provide possibility for some nice features. Keeping the project seperated however would be good to keep the project alive independently even when ilaris-online is not online anymore. So I think the api calls and snippet code should be seperated in a way, that it's easy to remove and/or can be configured to use optionally. Hardcode it everywhere, like the google login was can become anoying. To have some time to test and implement it I put it on milestone for v1 and it could be shifted even further. This issue is to discuss the general approach, where individual related features can be linked: