Cloudron Forum

I'm self-hosting Zulip and would love to see it packaged for Cloudron. I'm open to sponsoring the work or contracting someone to make this happen. If anyone from the community or the Cloudron team is interested, please reach out to alex[at]modos.tech, and we can figure out the details together. Thanks.

Zulip is one of the applications I use daily and is essential to me. I'm using it for an open-source project, self-hosted. I would be thrilled if it could be an application I could install on Cloudron and use with n8n, Baserow, Jitsi, and other applications available in Cloudron.

Some of the best examples/use cases of using Zulip and its advantages are below:

• How RC uses Zulip
• How to make remote work: Zulip

In addition, they recently have added a public access option, where anyone can view a topic without signing up simply by sharing a link.

One of the largest reasons I use Zulip is to have chats and our information organized as a knowledge base, it's our community's source of truth.

I hope the team considers making Zulip available on Cloudron.

Thank you for all of your hard work and support.

Regards,
Alex

Some recent updates related to Zulip:

• Zulip has an officially supported, experimental docker image
• Zulip 7.0 was recently released: visual redesign, scheduling messages, streamlining messages, and more.

More information below:
https://zulip.readthedocs.io/en/stable/production/deployment.html#zulip-in-docker
https://github.com/zulip/docker-zulip
https://blog.zulip.com/2023/05/31/zulip-7-0-released/

@girish said in Baserow 1.9 and it's Dockerfile and packaging changes:

@nigel_baserow sorry for the late reply!

As @robi mentioned, all our apps are based on the same base image. This is mostly to maintain consistency and saves us a lot of developer time in terms of maintaining these images. The base image also needs to have many packages that are expected by the Cloudron tooling - the web terminal, upload, extract features all depend on the base image having various packages pre-installed.

In general, we are comfortable with the cloudron packaging and the upstream docker image diverging. From what we have seen, the goals of these images are quite different. Upstream images want to support a wide variety of configurations and have different optimizations in mind. The Cloudron image on the other hand is pre-configured (database, email, storage, auth etc) and has various security restrictions (read only file system, non-root user etc).

We are happy to make the changes needed to the cloudron packaging with your help (this is just a matter of adapting what you have written to the cloudron image, I think). So, I think 1) is the way to go. Another thing is that removing mjml service is not a problem at all. In fact, that is the advantage of cloudron packaging, the docker images can be thrown away and replaced with another as long as the docker image can handle the "data" from the previous version.

Hello, thank you for building Cloudron, and all of the work that has gone into it.

Baserow is one of the applications that I use a lot on Cloudron and I intend to use it further in combination with n8n and other applications.

What's the status of updating Baserow to 1.9 in Cloudron?

Thank you for your time and support.

Hi Cloudron Team,

I hope you're doing well. I noticed unusually large log files in the directory below:

/home/yellowtent/platformdata/logs/mongodb
 
app.log       → 24GB
app.log.1     → 12GB

1. Is there a known issue or misconfiguration that could cause these files to grow to this size?
2. If these are app-specific logs, what controls their retention and rotation?

Would appreciate guidance on how to clean these up and prevent future bloating safely.

Thank you for your time and support.

Best,
Alex

Hi Cloudron team,

I'm interested in using Metabase and Baserow together. From what I understand, Baserow uses PostgreSQL, and PostgreSQL is one of the official data sources supported by Metabase.

Could it be possible to connect both of these applications in Cloudron?

Thank you for your time and support.

Regards,
Alex

Can we use Documize as a multi-tenanted application on Cloudron?

From the documentation:

"Documize is a fully multi-tenanted application capable of serving multiple separated customers from within the same running instance.

A single Documize installation supports multiple tenants and identifies different tenants based upon URL.

• https://legal.example.org
• https://finance.example.org
• https://tech.example.org

A Documize user can have access to one or more tenants. Each tenants data is protected from the other tenants."

@james said in Unexpected Large Log Files in /home/yellowtent/platformdata/logs/mongodb:

Hello @alex-a-soto

It might be a good idea to clear the MongoDB logs, disable wekan to confirm if this is the issue.

Hi @james, I cleared the MongoDB logs, disabled Wekan, waited for about 10 minutes, and checked app.log and app.log.1, the file size stayed the same during that time.

I restarted Wekan and noticed that both log files began increasing in size again by about 1.0 MB in minutes.

The logs show repeated hello commands from Wekan to MongoDB that time out or wait for responses.

2025-06-10T19:04:51.245+00:00 - "Error while waiting for hello response"
2025-06-10T19:04:51.245+00:00 - "Slow query"
2025-06-10T19:04:51.245+00:00 - "Waiting for a hello response from a topology change or until deadline"

Hi @james, thank you for your support.

There is/was this issue https://forum.cloudron.io/topic/13361/after-ubuntu-22-24-upgrade-syslog-getting-spammed-and-grows-way-to-much-clogging-up-the-diskspace might be also the case here.

Needs to be validated.

I'll check to see if it's related to the Ubuntu upgrade.

I ran head -n 1 app.log and got a MongoDB log entry noting a find query by _id, labeled as a "slow query" even though it completed instantly (0ms).

What apps are you using?

n8n, Cal.com Nextcloud, Baserow, HedgeDoc, SOGo, Wekan

I started noticing this after installing Wekan.

@james @joseph Thank you. I've increased the memory of Wekan and MongoDB. I appreciate your support in troubleshooting. I'll monitor Wekan today and tomorrow to see if this makes a difference.