You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm seeking clarification on the usage of CKAN in relation to its licensing terms.
I intend to deploy CKAN on my personal server using the docker images provided in the repository ckan/ckan-docker. It's important to note that I have no intention of modifying the CKAN tool's code itself. Instead, my goal is to create a custom docker-compose configuration file and appropriately adjust the .env file to incorporate additional built-in CKAN plugins.
The setup involves configuring a docker-compose.yml file to connect a web application with CKAN. I plan to maintain this configuration within a private repository on GitLab.
Could someone please advise if this usage aligns with CKAN's AGPL license? If it does not comply, would it be acceptable to incorporate CKAN as a submodule within my private repository? Alternatively, if this approach violates the license, would it be necessary to make this setup publicly accessible?
Your insights on this matter would be greatly appreciated.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello CKAN Community,
I'm seeking clarification on the usage of CKAN in relation to its licensing terms.
I intend to deploy CKAN on my personal server using the docker images provided in the repository ckan/ckan-docker. It's important to note that I have no intention of modifying the CKAN tool's code itself. Instead, my goal is to create a custom docker-compose configuration file and appropriately adjust the .env file to incorporate additional built-in CKAN plugins.
The setup involves configuring a docker-compose.yml file to connect a web application with CKAN. I plan to maintain this configuration within a private repository on GitLab.
Could someone please advise if this usage aligns with CKAN's AGPL license? If it does not comply, would it be acceptable to incorporate CKAN as a submodule within my private repository? Alternatively, if this approach violates the license, would it be necessary to make this setup publicly accessible?
Your insights on this matter would be greatly appreciated.
Thank you for your help,
Migolek
Beta Was this translation helpful? Give feedback.
All reactions