AppFlowy

[jadudm]

Someone more familiar with packaging Cloudron apps would be able to answer better than me. However, I find that whenever a docker-compose.yml is involved, it is probably hard to move the app to Cloudron.

https://github.com/AppFlowy-IO/AppFlowy-Cloud/blob/main/docker-compose.yml

In this case:

• It wants nginx. That might be avoidable, or it might be serving static assets/code for the app.
• It wants minio. This could probably be accommodated by requiring users to run minio on their Cloudron before installing this.
• It wants postgres, which might be able to be leveraged from the internal stack.
• It wants redis. Again, possibly from the default stack... I can't remember.
• gotrue is an auth component from supabase. This will need its own container, and may (or may not) play nice with the SMTP/OAuth running on Cloudron.
• appflowy_cloud is the hosted app. It wants its own container, and configuration information for all of the services included.
• admin_frontend has its own Dockerfile. I haven't looked. Looks like more things.
• ai. I have no idea. It looks like it wants some kind of OpenAI. This is getting heavy in terms of resources.
• appflowy_history is... another Dockerfile. Looks like a rust application that has been Dockerized.

The problem, I think, is that Cloudron assumes/is structured such that applications run as single containers. The compose is suggesting that this application has a number of independent components. Perhaps those could be bundled up/run separately... but, it might be a real trick to make work.

This isn't to say it isn't possible, but that's what I see that needs to run, and it isn't clear to me that this is an easy app architecture to move over to Cloudron. YMMV, etc.

[Dont-Worry]

+1 for Appflowy. Very very high value added.

[plusone-nick]

@jadudm so what you're saying is implementing docker-compose into Cloudron would fix this and a ton of other use cases....🫡

[tgatellier]

+1 for this app, waiting so much to have it on cloudron

[micmc]

Seems like we may have missed this new Self-Hosted cloud version named AppFlowy Cloud.
https://docs.appflowy.io/docs/guides/appflowy/self-hosting-appflowy
https://github.com/AppFlowy-IO/AppFlowy-Cloud/blob/main/doc/DEPLOYMENT.md

While waiting for apps to be added to Cloudron, hopefully folks at least take the time to experiment by yourself and try to install the app yourself first on another server, that you might learn a thing or two, and eventually come to integrate apps to Cloudron yourself

[Dont-Worry]

@micmc I tried, many times actually. Never managed to make it work by myself. Maybe I'm stupid.. This is why I use cloudron..

[actuarch]

+1 for AppFlowy

[marcusquinn]

Updated the screenshots above, as it's developed a lot since I first posted this.

Does seem like a very high value win if we can get this packaged here.

[Gengar]

I've just discovered AppFlowy and this app seems awesome ! Would love to see it in Cloudron. I'm a notion power user, and I can't wait to ditch notion.

But as @jadudm said, seems like docker-compose based app are not easy to convert to a single dockerfile to work with Cloudron...

[Dont-Worry]

Would be very good to have it in Cloudron. Vikunja is good but a little bit too simplistic for business needs.

[robi]

@Gengar said in AppFlowy:

But as @jadudm said, seems like docker-compose based app are not easy to convert to a single dockerfile to work with Cloudron...

This conclusion is not correct.

Compose just means separate things being put together as one, and many devs don't know they don't need to do that with whatever docs the followed.

Hence a single dockerfile is just that, all the services set up in the right sequence in one.

This is what your computer does, right? Until you install a hypervisor or docker, etc to separate things out.

So it's not any more difficult, it's just more than one service to define and setup in the Cloudron way.

And we already have 3 digits of apps many of which need more than one service running for the App.

Tons of examples in at git.cloudron.io

[Gengar]

@robi Thanks for your clarification, and you're absolutely right that a docker-compose setup can be translated into a single Dockerfile. I didn’t mean to suggest it's impossible or overly complex from a technical point of view. It just seems to me, based on what I’ve read on the forum and what @jadudm pointed out, that apps originally built with docker-compose tend to require more work to adapt to Cloudron. So they don’t always feel like the easiest starting point compared to more straightforward "quick win" Dockerfile-based apps.

[robi]

@Gengar No worries, we're on the same page.

And no need to discourage anyone from trying.