|
|
Post by Admin on Jun 6, 2019 18:02:34 GMT
pushed past 1.0 and released 1.1.76 of the plugin today and updated the profile to go with it
This new release adds :
- networkRoles
- networkGroups
- better cors functionality
- fixes for ping service
I also have a build pipeline now so the builds will go smoother from now on (learned from my mistakes last time) and if anything comes up I can just add it to the build pipeline.
So all good and running smoothly.
Next up, 'bootstrapped tests'. Halfway done but got a little sidetracked with everything else on my plate.
Going to try to get them out the door in the next week.
|
|
|
|
Post by pekatete on Jun 14, 2019 11:11:17 GMT
Is there any documentation on multi-tenanting or is there an office role?
|
|
|
|
Post by Admin on Jun 17, 2019 15:12:42 GMT
Well multi-tenant can be handled through the subdomain. Pretty simple. But if you want to use the same login, you need to use multiple databases and separate that out. Hmmm... why dont I work on that today and push that out so the user/validation tables are all in separate database that can be shared; this will make multitenancy as simple as just setting the subdomain  Just added the issue github.com/orubel/Beapi-API-Framework/issues/112 |
|
|
|
Post by Admin on Jun 17, 2019 15:18:12 GMT
So once I add the multiple database, I'll put in a section on multi-tenant in the documentation as well. Was going to update documentation today anyway but I can put that off til tomorrow.
|
|
|
|
Post by pekatete on Jun 17, 2019 19:42:25 GMT
thanks and that was quick (I suppose as soon as you saw it!).
Will keep an eye out for the documentation and reach out if I have further queries.
|
|
|
|
Post by Admin on Jun 18, 2019 21:44:28 GMT
So I took a look at this and the multi-tenancy in Grails. (https://github.com/orubel/Beapi-API-Framework/issues/112)
First, you have to support multiple datasources. This in itself should not be hard in theory. Springboot does a great job of this and its a fairly simple solution... BUT...
GORM has bugs that have caused issues with this since 2016 (if you read through the tickets); their are several things that need to be implemented and should be implemented in Grails 4.0 (which is supposed to be out right now) but they just haven't gotten around to supporting.
This among other things is making me think I should just move the entire project to Spring-boot and dump Grails.
That doesn't mean I have to dump Groovy; I'll just do the MVC in Groovy to make things approachable and the rest in Java.
You are making me think my next major push is for a rewrite now that everything is fairly stable; would probably improve speed even more and increase community involvement.
|
|
|
|
Post by pekatete on Jun 18, 2019 21:56:19 GMT
Yes read the issue on GitHub. If indeed Grails 4.0 won't have the support required then maybe a re-write is in order.
Since you'll be doing all the work, I won't push you on this, in your time!
thanks again for looking.
|
|
|
|
Post by Admin on Jun 18, 2019 22:14:29 GMT
Well one of the other problems with multi-tenancy is that it these days, it is better to do it in the architecture rather than in the application. For example, you have a load balancer and a proxy that will route traffic based on the subdomain... and while the backend may be the EXACT SAME APPLICATION, you can have each one serve different data. This is the way I handle multitenancy these days. That really is a far better solutiuon for you It's also the way I built this to work. However, I have wanted to separate the user/auth db. The multiple datasources keeps being my bottleneck |
|
