4 ms·
I'd like to try using this at work for an internal tool but AGPL is a no go.
by hnaccy 5y ago
I'd like to try using this at work for an internal tool but AGPL is a no go.
- awwaiid 5y agoIf it is an internal tool what is the problem?
- McGlockenshire 5y agoAll of the AGPL bits are inside that docker container. You don't need to worry about AGPL contamination unless you're modifying the contents of the container. This type of software distributed this way is one of the ideal use cases for the AGPL, IMO.
- anaganisk 5y agoUnless you are making changes to its code. Im not sure how would it even affevt you? Also correct me if I am wrong about making source available with your modifications is not uploading it on github. It means your source must be available for your users in any form. If its an internal I dont even see what's the problem there. I would rather have good products on strict license. I rather dont want AWS to leach on this project and launch AWS Elastic Freetable.