Cloudron Forum

@timconsidine The world is moving to AI-enabled, whether we do or not. Given the Cloudron primary purpose is self-hosting, I expect that will need to move to including with GPUs and local models. I expect ARM is going to be significant in this, too, for smaller focused models.

Hello @imc67 Now we can start analysing. Edit the file /home/yellowtent/platformdata/mysql/custom.cnf and add the following lines: [mysqld] general_log = 1 slow_query_log = 1 Restart the MySQL service in the Cloudron Dashboard. The log files are stored at /home/yellowtent/platformdata/mysql/mysql.log and /home/yellowtent/platformdata/mysql/mysql-slow.log. Let it run for a day or more. Then you can download the log files and see what queries run very often causing disk I/O.

@girish One other thing [image: 1765711486331-screenshot-my-intranet-apes-org-uk-2025-12-14-11-23-31-resized.png] Seeing the menu to edit mailboxes is hidden as the list doesn't utilise the full screen. I thought this was an error at first, until I scrolled all the way to he bottom. The scroller doesn't show until reaching the bottom of the page. It is a pain to have to scroll down to move across to access the mailbox menu. Especially when deleting multiple mailboxes by domain. Although we found that using the left and right keys on the keyboard sometimes allowed for horizontal scrolling. But still a pain to have to move left and right to make sure you're deleting the correct mailbox or editing it. It would be so much easier to read if the list utilised the full screen.

Tried this on Yunohost and REALLY liked it. MUCH easier to manage than Invoice Ninja.

Probably some upstream bug . https://git.cloudron.io/packages/wordpress-developer-app/-/merge_requests/19 is also stuck for the same reason .

I put in a text-align , https://git.cloudron.io/platform/box/-/commit/b2f5110871781f7e50fd440ffd2d211b1768770e

As @avatar1024 said, the current OIDC/SSO installed instances will not get updates anymore. It will continue working for foreseeable future. Thnk of the current package visible in the app store as a totally different app. If you want to use the old app, put `stirlingpdf.frooodle.cloudronapp in the url bar after clicking on stirling.

The issue was that config.php had hardcoded database credentials. Possibly from a very early package of HumHub which didn't use environment variables.

@firmansi this is fixed in 9.0.15 . see https://forum.cloudron.io/topic/14687/how-to-integrate-openid-cloudron-with-cloudflare-access

@micmc aha - i'm iterating fast and pretty-much daily What you're getting, is what I'm using every day now, so it's all being refined from real-life use, and self-improving using the @agent-review subagent. I've added a ton for development workflow best-practice with git, to help anyone vibe-coding stay better organised and safer with their workflow. Issues and PRs welcome. It is all opinionated for the tools i work with most, but hopefully all self-explanatory enough to see how to extend for your own needs. I'm having a ton of fun with it. Hope you all enjoy the journey as much as I am. It really is becoming the dream team

@LoudLemur Yeah AnythingLLM is amazing, I believe much cleaner and intuitive than Open WebUI. One can install it online as well via Coolify or EasyPanel and it's quite impressive out of the box too. Thanks for sharing this summary.

Big Love @d19dotca

@luisegundo can you not just "print to PDF" ?

Hello @luisegundo To get the PostgreSQL credentials of the nocodb app open the web terminal of the nocodb app: [image: 1765647416723-f1418f0e-ffb5-409b-9680-b28964c09c8a-image.png] In this terminal copy and paste the following command and press enter: printenv | grep -i POSTGRESQL You will get an output like this: CLOUDRON_POSTGRESQL_URL=postgres://user876d5ae64c9d44a4979aafbfffb68286:25025a6a57810a29ae4a052a416291bda191d339b63f129e42a512e07ba0b8f36fe6fccddbf3f1c15fd607d6d81d84ab9a1fee67547ff498890405a594d1bdd6@postgresql/db876d5ae64c9d44a4979aafbfffb68286 CLOUDRON_POSTGRESQL_DATABASE=db876d5ae64c9d44a4979aafbfffb68286 CLOUDRON_POSTGRESQL_PASSWORD=25025a6a57810a29ae4a052a416291bda191d339b63f129e42a512e07ba0b8f36fe6fccddbf3f1c15fd607d6d81d84ab9a1fee67547ff498890405a594d1bdd6 CLOUDRON_POSTGRESQL_USERNAME=user876d5ae64c9d44a4979aafbfffb68286 CLOUDRON_POSTGRESQL_HOST=postgresql CLOUDRON_POSTGRESQL_PORT=5432 Copy and save this output somewhere, you will need it later. Now in the metabase web UI I can add a database with the previous credentials. Tip, use the CLOUDRON_POSTGRESQL_URL and put in the Connection string (optional) field in Metabase and give it a descriptive display name instead of the long generated string db876d5ae64c9d44a4979aafbfffb68286: [image: 1765647679218-e02db919-16e8-4c93-9bd2-417281768c96-image-resized.png] Now I can access the NocoDB PostgreSQL database in Metabase: [image: 1765647746938-0c1362ae-2245-4a37-a241-26318225a2d0-image-resized.png] Is this what you needed?

Hello @vk182 @vk182 said in Hiding apps behind the proxy app to enable cloudron authentication: Can you please point me to the documentation on how this can be done? I understand now that and app updates itself, isn't it? I have done so already here said in Hiding apps behind the proxy app to enable cloudron authentication: I did a recent post about this, see: https://forum.cloudron.io/post/115963