Henry Weismann
Henry Weismann
If we do a separate module i dont think licensing conflicts are such an issue if its available from marketplace and not in the core so I would consider using:...
yes i saw that but for some reason i thought it supported like 3 providers, now i see its very good: https://socialiteproviders.com/about/
100% for lara branch
https://github.com/FOSSBilling/FOSSBilling/issues/303
supported by https://github.com/FOSSBilling/FOSSBilling/issues/303
Interesting +1
if we do do api: https://vyuldashev.github.io/laravel-openapi/ supporting swagger/openapi would be nice for auto documentation
ok so then a standardized api in front of a Cpanel, Directadmin, Plesk, Hestia or Whatever. pluginized library ...am i getting that right?
i think thats the point, how do you think the api i mentioned does it ...saying you cant do a standardized api is imho not 100% true, all it is...
sorry i mentioned the standarized api for shopping carts elsewhere, but this is what i mean, an example of what i mean: https://api2cart.com/ See this: https://docs.api2cart.com/post/interactive-docs?version=v1.1 It is one api...