4 ms·

Here's one way to by pass GPL restrictions when you must use it for whatever reason. Create a separate service with all the GPL codes. Write your own micro ser

Here's one way to by pass GPL restrictions when you must use it for whatever reason. Create a separate service with all the GPL codes. Write your own micro service API to communicate with it. And then open source your micro service code without opening up your propitiatory part. Of course someone else should have thought of it before. Searched and found first hit on stackoverflow. That says it's OK at least when used in a separate VM, no shared memory between the two. https://law.stackexchange.com/questions/40420/gpl-licensed-code-as-separate-process https://law.stackexchange.com/questions/40420/gpl-licensed-c...

jeroenhd 4y ago
If you run the server locally you'll still need to hand out the GPL'd code but that would likely work. The moment you include an AGPL licensed piece of code this no longer works, though. The post only mentions GPL and LGPL, but they're also violating other licenses as pointed out here in the comments. I wouldn't be surprised if there's also an AGPL licensed piece of code in there that makes this workaround impossible. Honestly, this workaround sounds like a lot of work to maintain long term while also putting you at the whims of library maintainers who may just switch out the license on you with newer versions, leaving you to do the maintenance and security monitoring of your dependency. If you need to put so much work into avoiding complying with the license you should consider just writing your own code instead.