AGPLv3 free software with an obligation to distribute derived works under a compatible licence. Hosting cuplbackend on a network counts as distribution, so you must be willing to provide source code on request.
FAQ: I work for a business. How do I integrate cuplbackend with proprietary backend services?
This is no problem. The integration can be done at the API level. There is no need to change cuplbackend itself.
You can create a custom user interface and call any number of your own APIs by adapting the frontend, which is released under a permissive Apache 2.0 licence. There is no obligation to release source-code for the frontend; it is not an essential part of our re-usable platform.
Endpoints and webhooks on cuplbackend will give developers flexibility to build their own applications.
FAQ: Can you host this software for us, so that we do not have to install it on our network?
Yes! Talk to us about our SaaS offering.
cuplbackend can be run from a Docker image. First pull it from DockerHub.
docker pull cupl/backend
Some environment variables must be set for it to run. These specify the database URI + password etc.
You are encouraged to:
- Fork the GitHub repository to make your own private copy.
- Clone the fork.
To make a change:
- Submit an issue and get feedback. It is recommended this be done before any code is written.
- Make the code change.
- Submit a pull request to the dev branch.