3 ms·
Yes, the distinction is the networking. If you make changes to Nocobase and provide an app over the network using that changed code, you would need to provide y
by andyferris 2y ago
Yes, the distinction is the networking. If you make changes to Nocobase and provide an app over the network using that changed code, you would need to provide your fork of Nocobase.
AFAICT Nocobase is the platform here. Just like when you use linix, compile your code with GCC, or use happen to use a bash script in production, you don't need to provide your application and infrastructure code along with your app, you shouldn't need to provide your application code (or plugin code?) written for Nocobase. Right?
- andyferris 2y agoApparently I was a bit wrong - the plugins are not seperate (if you want to write closed-source plugins you should use the commerical license, not the AGPL). The schema and data and UI configs should be private though - so enough to build a wiki or notion-like site, and set up some integrations based on the free plugins. https://www.nocobase.com/commercial.html https://www.nocobase.com/commercial.html