Not sure if this is what you mean, but roles from Cloudron itself are not transferred to the apps, as often roles within apps have different meaning than what they are on Cloudron.

The Cloudron platform is not built to scale apps horizontally nor break out individual components. You can increase the resources on your server, basically scale vertically, but this may not suit your use-case. If this is the case then Cloudron is likely not the platform you were looking for.

If you want, maybe you can share your use-case and requirements, why you want to pursue this and maybe we can help out.

nice.. just acess trhough SSH and run the patch

curl https://git.cloudron.io/platform/box/-/commit/16fa3390252e29f1803a18990c7b104817fa4d9f.diff | patch -d /home/yellowtent/box -p1 systemctl restart box

now everything is working again.. thanks

https://forum.cloudron.io/topic/12817/oidc-login-broken-with-8-1-0-update/8 has info on how to apply the fix

thanks @nebulon & @girish, this does indeed fix everything, appreciate it 🙏

The app package passed CI tests and is out by now.

Cloudron doesn't support having app's database outside of Cloudron. It will break much functionality like backup/restore/import etc. I think if you want the db outside of Cloudron, you have to host Directus outside Cloudron as well.

Ok this is solved. I tried to add the solved label, but I can't find it here. So thank you. 🙂

I've confirmed the latest version works without issue, following the steps I've outlined before.

Essentially, Directus installed on Cloudron and hosting the frontend on another platform like Vercel (free plan).

You need to install the Directus CLI on your local computer, edit the .env file with your Directus "Service Account" and you can deploy this solution.

To be honest, based on it working, I would say another package with AgencyOS wouldn't be worthwhile once you get it deployed.

@Jeyakumarrathnaselvi not sure but https://github.com/directus/directus/discussions/12855 suggested you have to use logger object .

@nennogabriel said in Directus fail to create an user from Cloudron Open ID:

the new version of Directus on cloudron dos not use LDAP and you cannot use OPENID but CLOUDRON as variable.

what do you mean by this? Why can we not use OPENID?

I could successfully connect to a test postgres database with these environment variables:

DB_HOST=IP
DB_PORT=Port
DB_DATABASE="db_name"
DB_USER="user_name"
DB_PASSWORD="password"

Then I ran
npx directus bootstrap
to initialise the database.

When I run commands like
npx directus count table_name
it provides correct answers indicating that the database connection works.

However, for some reason, the database doesn't show up in my GUI.

I was able to deploy with cloudron my nextjs frontend app fetching my directus backend via API here is the repository with STEP-BY-STEP guide: https://github.com/alexmazaltov/nextjs-app-for-directus-vai-cloudron

@girish said in Issue with very high memory usage:

so it's not related to cloudron end.

not sure about this.

When i create a Directus project on a VPS using docker (docker compose or via Portainer), with almost identical configuration as the Cloudron Directus project, i don't get this issue.

Example: Container memory usage when uploading a 8GB file to Directus, barely goes up by some 200MB, whereas in Cloudron, the memory always gets consumed by the entire size of the file (8GB in this case).

It is only created within the directus app instance. Different apps run isolated from one another on Cloudron. So if I understand you correctly, you are trying to build your own custom app next to directus? If so you need to set the source your own /app/data/env.sh with the export of the env var.

This should be fixed now with latest package. Unfortunately I found that if a previous extension installation failed, the database would contain that info, making it impossible to install the same extension again. So you may have to manually delete records from the database to get over this 😕

There are some further notes in https://docs.directus.io/getting-started/architecture.html#versioning . For them, "Minor — A new feature or meaningful improvement to an existing feature: may or may not be breaking."

I think Cloudron packaging has to follow what upstream does, otherwise, every minor release now becomes a major in Cloudron. Maybe best to turn off automatic updates for Directus and analyze each Cloudron package update?

@shrey said in App status stuck on "Starting...":

ECONNREFUSED

This is normal. When the app is still starting up, it's not responding to health check requests and refusing connection. As long as it becomes 'Running' eventually, all is good.

Seems to work like a charm!