Cloudron Forum

Hi Everyone,
We saw this as we had the same issue and we posted a request with Taiga to get this resolved.
Taiga show the status as Ready to Release...
https://tree.taiga.io/project/taiga/issue/5196
Perhaps this can be put into Cloudron now as we are big users of Taiga and need to keep it up to date, thanks!
Hope this helps.

@girish thanks, I'll chase them next week if they haven't by then

I run 5 or so live Cloudrons across the businesses I'm responsible for and we've been looking for a replacement Wiki to switch to as we know Confluence on-premise is going away.

When selecting candidates for a project like this I always start by looking at the products on Cloudron,

• firstly because it is quick and easy to install and try them (thanks guys, Cloudron is awesome!)

• secondly because you guys have already gone through a process of vetting out the not so good products - if it has made it to Cloudron is must have merit!

I think where the case requires a larger/more complex use Confluence is a long way ahead of most of the other alternative Wikis already on Cloudron so I looked at a lot of other OS Wikis to find a better option.

XWiki does appear to be everything a larger Wiki needs there is also mention of a Confluence import - an essential tool if anyone is ever to migrate from Confluence with years of knowledge embedded in the platform.

There is also a Docker implementation of XWiki, the trend is now to deploy on Docker.

I was wondering if we are any closer to having XWiki on Cloudron...

@nebulon, version 3.2.0 has an issue that breaks Leantime if upgrade from an earlier version without first disabling all the plugins and deleting some files/folders. All very well, however the first you know about this is when the automatic upgrade has run and broken Leantime, by which time it is too late.
@marcelfolaron has kindly released a fix in version 3.2.1 which will allow us to get back up and running, however we cannot manually install it as we don't want to break the Cloudron updates system.
Can you give an idea on when you might be able to pull this new version?
Thank you for your help

@ruihildt

Although they have many similarities in the things they do they are very different beasts to use. We found Confluence to be much smoother for end users to edit content, users could simply type what they liked, paste content from other documents and retain the formatting. More than one person could edit a document at the same time. What you saw was what would be visible instantly when saved.

I am not a Wiki.js advanced user, but my impressions were very different. Editing documents was much more like creating web content than using. You have to click the edit button, wait for it to display the edit page and then find where you were when you decided to update the content.

When you are done and then there was a long pause to render the page after you publish it, stopping you from working in the meantime - this was on a 16 processor 48GB RAM SSD-NVMe server, so hardware wasn't the issue.

All this is OK for users who consume content or those who statically create content with occasional edits, but not ideal when you want your non-Wiki savvy users to see content that needs correcting and simply want to click in the page where they see the error, change it then save it.

The big challenge for us is persuading our users to contribute and update content. It has to be a slick and pleasant experience.

@marcusquinn yep, thanks, we tried BS, simple to use and great for smaller projects. Not really suited to our needs in this case

@timconsidine yes, agreed, everyone will always want their own favorite one added.

For us we don't have a favorite yet, but we have a clear requirement for something that is open source, self hosting and is fully featured enough to make it a comprehensive replacement for Confluence.

I may be mistaken, but Wikiss is aimed at a different use case and is does not compete in this space. As @nebulon says it is a lightweight PHP system