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

Thanks @fanvyr this saved my bacon
My box got 'stuck' upgrading from 8.x to 9.x so I used SSH to reboot.

db-migrate check as above said there were 11 to go, starting from:

[INFO] Migrations to run: [
'20250618200400-fix-charset-collate',

db-migrate up finished them all and a reboot got my box running again. Thanks for posting this!

@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

Hi Forum,

I can't seem to get Seaweed to use my available disk space or more than one bucket. Has anyone had the same issue?

Background: I have been looking to replace my Minio S3 service with either garage SeaweedFS or RustFS and choose Seaweed. My main use case is to use S3 for tarball backups and I have a server with 14TB of space to use for this. Minio was good for this, however it no longer has a future in the OS community. SeeweedFS works well and is good to use, plus it is stable. RustFS also works well, has fewer features (that I probably don't use) but is not stable yet.

Issues: After installing Seaweed it works fine as installed, but it appears to be set to a maximum useable limit of 8Gb and also I get errors if I try to use any second bucket at all - no free volumes. I see in file manager and the Seaweed dash that I already have 8 volumes. The my first Cloudron Server backup saves fine, but fail after 8 Gb, my second Cloudron server fails if I try to set it to a different bucket with the no free volumes error in the logs.

Using weed volume.list I can see the volume size limit is set to 1024 MB (also visible in the dashboard) and the max number of volumes is set to 8. I have not been able to increase these and it appears that the Cloudron App has set some parameters in the start script which I haven't found a way of overriding in env.sh.

I suspect I need to override the defaults to expand the usable space, for example I could do 430 volumes × 30,000 MB = 12,900,000 MB => 12,900,000 MB = 12.30 TB of raw data storage, leaving headroom for indexes etc, but I can't seem to override these in the Cloudron App:

• volumeSizeLimitMB - I understand there is a build limit to 30Gb (30000) to do with 4 bit sizes

• maxVolumeCounts - either to 0 for auto or a sufficiently large number that x the Size uses the available disk space

I have tried numerous options in env.sh and none change the setting, even if I remove the existing files, volumes and collections. Options include:
export WEED_VOLUME_ARGS="-max=126" or export WEED_MASTER_ARGS="-volumeSizeLimitMB=30000 -maxVolumeCounts=hdd:126"

I can achieve this with a custom start script called from env.sh (which shows it is being run), but of course this breaks everything Cloudron. Is there a way to do this, or am I missing something?

If not, can you expose the variables so that we can achieve using the available disk space and multiple buckets (collections)?

Thanks in advance!!!

Thanks @james I did try that before, then restarted the app and it didn't work, however I now unmounted then deleted the volume (*.idx, *.dat, *.vif (left *.uuid) and restarted it and it seems to have worked - I can see over 15 volumes.
I'll see how it goes with the backups tonight!
Thanks for your help

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...

Hi @timconsidine,
Did you ever share the AnythingLLM?
I was interested in trying it, but I can't see it on https://ca.cloudron.io/

It would be great to spin it up and compare it to the OpenWebUI and LibreChat

If you need a license to integrate this I'm sure Marcel will oblige.
As it is an additional cost option, would you approach this in the same way as Cloudron did for FreeScout, where by default it installs with the app managing its own users, unless the license is purchased?

Hi @nebulon I think the app does support OIDC, at least according to this article https://marketplace.leantime.io/product/installation-auth-provider/
Choice of LDAP (OL or AD), OIDC or Google SSO. Works with the open source installation: https://marketplace.leantime.io/product/leantime-open-source-installation/

Thank you @girish and @marcelfolaron, I updated my test system with the fix and it worked fine, so I have updated production ones too.
That was resolved remarkably quickly and saved me a lot of strife, amazing, thanks again

@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

Thanks for looking into this @timconsidine.
I thought about your comments and then I installed LibreChat. I will see how I get on with that first.