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

[pathab]

• Main Page: https://www.fizzy.do/
• Git: https://github.com/basecamp/fizzy
• Licence: O'Saasy License
• Dockerfile: ?
• Demo: https://www.fizzy.do/

---

• Summary: Kanban as it should be, not as it has been. Fizzy is a fresh take on cards and columns, with a few twists, human-nature inspired defaults, and a vibrant interface that’s the opposite of the bland and boring software the industry has been flinging at you for years.

---

• Notes: Really like the idea and the concept and love to selfhost on my cloudron.

---

• Alternative to / Libhunt link: Trello, Asana, Jira,
• Screenshots:

[andreasdueren]

Not sure if the license is compatible with cloudron:

No licensee or downstream recipient may use the Software (including any modified or derivative versions) to directly compete with the original Licensor by offering it to third parties as a hosted, managed, or Software-as-a-Service (SaaS) product or cloud service where the primary value of the service is the functionality of the Software itself.

[jdaviescoates]

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

where the primary value of the service is the functionality of the Software itself.

I guess it depends on what this bit means?

The primary value of a Cloudron server would not become the functionality of Fizzy itself, even if Fizzy were in the Cloudron app store.

Reads to me like "don't directly compete with us, otherwise fine".

[timconsidine]

I agree with @jdaviescoates

My reading of that licence wording is the user who installs Fizzy to Cloudron must not then sell / rent access to their Fizzy instance as a service (competing with original Licensor).

Basically own (personal/group/business) use internal to the Cloudron hoster is OK, but they must not provide access as a paid SaaS.

I don't recalll which other app on Cloudron has similar provisions, but I am pretty sure there's at least one like that.

[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?

[pathab]

@luckym Yep, it's been working great. I use it privately every day and still run it on my Cloudron. I also keep the repo updated regularly, and so far every update has gone smoothly without any issues.

Is there something specific you're wondering about?

[luckym]

@pathab Very cool to hear! I'm thinking about trying it out as a Kanban app for a small team so cool to hear it's been working just fine on Cloudron

Form the upstream repo it looks like they release multiple times a day without any versioning scheme. Do you just sporadically rebase every few days or how do you stay on the latest version while making sure it doesn't break?

[jdaviescoates]

@staff is this already on the "add to official app store" roadmap?

[pathab]

@luckym So far I've mostly just pulled the latest changes from upstream sporadically and merged them into the repo without overwriting my Cloudron-specific adjustments.

With Cloudron updates you can always roll back if something breaks, so that makes it a bit less risky. But to be honest, it has always worked fine so far. Proper testing for the Cloudron package would definitely make sense though.

Recently I set up my OpenClaw to check and sync upstream weekly, which helps keeping things more up to date automatically

[james]

Hello @pathab
With Cloudron 9.1 we have added community app support.
Please check the latest documentation for package publishing https://docs.cloudron.io/packaging/publishing
Could you update your repo to include these changes?

[pathab]

@james The community apps feature completely went past me...that's a great addition!

I've just updated the repo to support the new publishing setup. After a few initial hiccups I managed to get everything sorted out. You should now be able to install it via:

https://raw.githubusercontent.com/patattzel/fizzy-cloudron/refs/heads/main/CloudronVersions.json

I've tested it myself and it seems to work. Please let me know if anything doesn't work as expected. Happy to hear if it succeeds on your side as well.

Please also keep the O'Saasy licensing in mind!