AGPL License Questions

[mentosan]

Hello

I have some questions related to the licensing model of Nextcloud.
My situation:

• I am building a cloud commercial app that uses the file sync part of Nextcloud
• I am having an own Docker image that uses Nextcloud image as a base
• the image is running some apt commands, and declares a new ENTRYPOINT (a custom entrypoint.sh that executes some scripts, enables/disables some apps, calls several occ commands and runs the base entrypoint.sh as well)
• beside the custom image I also have few config files (redis, theming related, etc.)

My image is deployed using the Nextcloud Helm Chart to a AKS cluster, as part of a microservices-based application.

Considering this scenario, is there something required to be published from my side, from the AGPL perspective? Do I need to publish my entrypoint.sh?

TIA

[tflidd]

We are not a forum with legal experts.

As far as I read, you did not change the Nextcloud code? Configuration files can change, so they alone should be no problem. Then you might check at which point deployment scripts are/can be part of it.

If you don’t want to take any risk, and if you have a way to configure Nextcloud more easily, it might be interesting for others and sharing might be benefitial for the community (and you perhaps get some feedback on further improvements).