AppFlowy
-
+1 for this app, waiting so much to have it on cloudron
-
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.mdWhile 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
-
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.mdWhile 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
@micmc I tried, many times actually. Never managed to make it work by myself. Maybe I'm stupid.. This is why I use cloudron..
-
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.
-
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...
-
Would be very good to have it in Cloudron. Vikunja is good but a little bit too simplistic for business needs.
-
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...
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
-
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
@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 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.