Fizzy on Cloudron - the Kanban tracking tool for issues and ideas by 37signals

[necrevistonnezr]

Hashicorp (now IBM) Vault (and all other Hashicorp products such as Terraform) e.g. has a similar license, the BUSL.
Other examples with similar licenses are MongoDB, Kibana, Elasticsearch, Redis…

Here’s a good overview: https://www.goodwinlaw.com/en/insights/publications/2024/09/insights-practices-moving-away-from-open-source-trends-in-licensing

[pathab]

I’ve just finished packaging Fizzy for Cloudron myself and the app is already running great on my instance

If anyone is interested, here are the Git repo and Docker image:
Git: https://github.com/patattzel/fizzy-cloudron
Docker Hub: https://hub.docker.com/r/pathab/fizzy-cloudron

It’s still a bit quick and dirty, but fully functional. Features like “first user becomes admin” and disabled signup are already implemented. More refinements will follow.

Regarding the license discussion:
From my perspective, this should not be an issue for Cloudron. Cloudron isn’t offering Fizzy as a hosted SaaS product. It simply enables users to self-host the software on their own servers.

[necrevistonnezr]

True, not a problem for Cloudron; but as with other such licensed software, it can be a problem for those Cloudron customers who are providers or resellers themselves.

[pathab]

Good point.

It would actually be helpful if apps with such licenses were explicitly marked in Cloudron, or if there were a setting/flag for reseller environments to warn about license restrictions before installation.

[zonzonzon]

I tried fizzy; overall it’s very simple, and it keeps our minds from being distracted by too many features. However, I think that at its current stage of development, the chance that the Cloudron team will package this app is extremely low.

[jdaviescoates]

@zonzonzon said in Fizzy on Cloudron - the Kanban tracking tool for issues and ideas by 37signals:

However, I think that at its current stage of development, the chance that the Cloudron team will package this app is extremely low.

Why, given that @pathab has already packaged it?

[pathab]

I’ve actually been running Fizzy on my own Cloudron instance continuously since the start of this forum thread.

The project has seen a lot of updates since then and is being actively pushed forward. So far I haven’t had any issues keeping my fork in sync with the latest releases, and the recent versions have been stable for me in day-to-day use.

If anyone wants to try it out themselves, you can install it on your own Cloudron instance via the Cloudron CLI with:

cloudron install --image pathab/fizzy-cloudron:latest

So from a packager’s perspective, it’s been very workable and maintainable.

[timconsidine]

So from a packager’s perspective, it’s been very workable and maintainable.

Well done !

@pathab said in Fizzy on Cloudron - the Kanban tracking tool for issues and ideas by 37signals:

If anyone wants to try it out themselves,

the user will also need the relevant CloudronManifest.json as well, and maybe any files it references (e.g. POSTINSTALL.md).

I can add it to my custom app installer a bit later, unless you prefer me not to do so.

[pathab]

The Docker image is already packaged specifically for Cloudron and includes the CloudronManifest.json, so no additional manifest is required for installation when using the image.

Feel free to add it to your custom installer if that’s useful for users, but everything needed is already bundled in the image itself.

Repo is here: said in Fizzy on Cloudron - the Kanban tracking tool for issues and ideas by 37signals:

Git: https://github.com/patattzel/fizzy-cloudron

[luckym]

@pathab Out of curiosity how has Fizzy been working for you? Are you still running it on your Cloudron?