Docs - Alternative to Notion / Outline with OIDC, GDPR compliant, PDF Export (with template) etc...
-
Agreed. I'm not offering thoughts from a spirit of "GIVE UP!," by any means. It is more from the perspective of "I think this one is trickier than it seems at first glance."
But, I am still learning. So, the staff may say "this is actually easy!" Or, they might say "Yep, it's kinda tricky." And, as a result, we all learn more.
-
@jadudm Thanks for your further input. It helps me forming a better understanding whatever the outcome of this discussion is.
That packaging apps in general and maybe this one in particular has a resource cost (time, money etc..) is no doubt of mine. So I am already grateful for the time you, others, everyone is spending considering this.
I am looking forward to the input of others too and @staff if possible, to see if this is a "yay or nay" situation or if there is more nuance to it.
I would also still be keen in exploring to which extend relaying information upstream might have an influence on packaging this for Cloudron.
@Neiluj said in Docs - Alternative to Notion / Outline with OIDC, GDPR compliant, PDF Export (with template) etc...:
I would also still be keen in exploring to which extend relaying information upstream might have an influence on packaging this for Cloudron.
You can always make the request on their github as one person there might be interested in helping and knowledgeable about making a package. But yes it would be great a stir from @staff here on whether this looks doable at all with the current Cloudron infrastructure. This app does look great and more open than outline (which is pretty great too, but with too many restrictions on the self-hosted version).
-
v3.3 is out: https://github.com/suitenumerique/docs/releases/tag/v3.3.0
Also mentioned in the Self-Host github section:"In the works: Docker Compose, YunoHost"
Would be great to see Cloudron in there.
-
I agree with you, now if you compare the NextCloud compose setup https://github.com/nextcloud/docker?tab=readme-ov-file#running-this-image-with-docker-compose with the one for Docs : https://github.com/suitenumerique/docs/blob/main/docker-compose.yml you will notice that due to the plethora of services and setup required for Docs to work, this is not so-easy to port Docs on Cloudron. Not technically impossible
, but still there is lot of chirurgy required. I guess it could take days worth of work (testing and rework and hacks) just to make it work til it breaks on next major upgrade. I guess at this point it's likely best to run Docs on a dedicated VPS rather than risking having unstable Docs on Cloudron. -
I agree with you, now if you compare the NextCloud compose setup https://github.com/nextcloud/docker?tab=readme-ov-file#running-this-image-with-docker-compose with the one for Docs : https://github.com/suitenumerique/docs/blob/main/docker-compose.yml you will notice that due to the plethora of services and setup required for Docs to work, this is not so-easy to port Docs on Cloudron. Not technically impossible
, but still there is lot of chirurgy required. I guess it could take days worth of work (testing and rework and hacks) just to make it work til it breaks on next major upgrade. I guess at this point it's likely best to run Docs on a dedicated VPS rather than risking having unstable Docs on Cloudron.@SansGuidon - thanks for your reply.
Just to be clear: I am not in hiding and know/understand that in the current state, it would take an important amount of work to make this happen on Cloudron.I suppose I am coming from a slightly different angle: if they mentioned that Docker Compose and YunoHost are work in progress, then they might be open to also work on making it happen for Cloudron and thus make some accommodating changes from their end too -> "going at it from both side and we meet in the middle" kind of situation.
However, this would ask someone with Cloudron packaging / deployment to get in touch with them and discuss what is possible.
-
I think shipping for YunoHost and Docker compose almost is similar work for them, while shipping for Cloudron which is not packaging with Docker Compose at all, would take them too much work. A bit like shipping a video game for BSD or Linux for a couple users, while your main market is at ease using Windows. Not only the initial work would be plenty, but also the maintenance for them, without having lot of ROI, would be a decision factor. Thus if we want such app on Cloudron, which is less known, we will likely need to do the work ourselves, because the way Cloudron package apps is a specific format which is not compatible with Docker compose at all.
EDIT: Related = https://forum.cloudron.io/topic/11580/support-for-docker-compose/3
-
I am also following their matrix channel and the app seems to be still under heavy development. My idea was to package it once they remove the beta tag on their website, but maybe we can look into the packaging side already earlier.
