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!

@samsls Thanks for following up with me on this! I used the Directus CLI with a Token for the admin account to import the data into a "default vanilla installation of Directus". Everything imported without any issues. Afterwards, I deployed the front end using Vercel from a private GitHub repo. Based on the reply from @girish, I put some additional configuration into the env.sh file and restarted Directus. export CORS_ENABLED="true" export CORS_ORIGIN="domain1.com,app-name.vercel.app" export CORS_METHODS="GET,POST,PATCH,DELETE,OPTIONS" export CORS_ALLOWED_HEADERS="Content-Type,Authorization" export CORS_EXPOSED_HEADERS="Content-Range" export CORS_CREDENTIALS="true" export CORS_MAX_AGE="18000" I've placed that into the env.sh as a wide-open test to at least see if I could get it working, but no luck. I know there are some other options, that you can force some of these settings into your Vercel deployment using the vercel.json file, but haven't gotten to that yet. There are some open issues that it seems they're looking into based on their GitHub. CORS issues for client portal in "PROD" like deployment Fetch the data from the server side instead of the client?

Yes seems to work thank you!

Thank you for helping me make it work. Strange this .mjs thing with them, I'm going to open an issue with them.

Those are only container upper limits, not what the apps will use. You can significantly increase the size of the swap file for more headroom, but things will slow down while swapping. You'll want more RAM as certain apps will use a lot more when you start heavier use. Cost wise, there are server providers that max RAM such as Contabo and SSDNodes at a decent price.

Directus is using postgres on Cloudron, see https://git.cloudron.io/cloudron/directus-app/-/blob/master/CloudronManifest.json#L15 Regarding the ping, took me a bit to realize that you have to hover over that wifi signal strength icon. However on a fresh install here on a not so beefy server it shows values around 50ms. But more importantly I am not actually sure what this represents and what the usefulness of this is.

I've found this: https://docs.cloudron.io/apps/directus/ Example Link is not working: https://github.com/directus/directus/blob/main/api/example.env

@pbischoff said in Scaling/vCPU core usage of Directus in Cloudron: But this is a problem for almost every node.js app of the cloudron App Store, isn't it? Do they all use only one vCPU core? Apps like NodeBB (this forum) support so called cluster mode - https://nodejs.org/api/cluster.html . Essentially, this creates worker threads to spread load across CPU. This is part of nodejs. But to keep in mind, nodejs by itself can handle quite a bit of parallelism with just one CPU. Most of the work done by the main process is just http request processing. This is usually I/O bound and not CPU bound. Nodejs being asynchronous can handle requests in parallel in just one process quite easily. We are talking about 1000s of requests a second. Many other nodejs apps like Cloudron code itself, peertube, offload the processing of static assets to a side installation of nginx. So, when downloading images/css files etc, it doesn't even hit nodejs. When node code has to do heavy work, it usually just puts it in a queue and the queue handler is a separate process (which can thus be restarted and killed easily). The queue handler will use another cpu core. For directus, I am not an expert on the app. But, you want to maybe use some worker thread or queue or something like that to make use of more CPUs.

@girish said in Unable to connect to a DigitalOcean managed database: None of the feature like backup/restore will work So far, they've been working fine. Because, all that's required to be backed up in such cases is the app code. Of course, as the database is external, it is accepted that the backup system is external & independent to Cloudron. @girish said in Unable to connect to a DigitalOcean managed database: Not an expert on the apps and I don't know if it's the main purpose. But they work just fine with fresh databases as well where you use it like a nocode/locode app. Yes, pairing up with external databases is indeed, one of the primary features of these apps. And using a fresh database is just one of the features, and not always preferred. You might want to state clearly and prominently, particularly in the cases of such apps, that external connections are not allowed/recommended.

The latest package has a higher default memory limit and is more reliable now during initial setup. So please try to install a fresh instance.

@devtron this should be out now. 1.24.1-2 is the correct package.

Same as https://forum.cloudron.io/topic/8451/unable-to-update-automatically-or-manually

@girish Thanks! That was hasty on my part Yeah, i've always used the .env setup with a docker-compose install of Directus.

@girish Maybe you could add those steps to the help section?

@girish happy to report that this is working like a charm, thanks a lot!

I'm coming back to this because I'm still confused. I have a remotely hosted database. I want to build an admin on top of that. That database must continue to be remotely hosted. Can I build that admin using Directus on Cloudron? If so, any pointers would be appreciated. Thank you!

@dev-cb I know you've already swapped, but wish I had seen this a few days ago. I run a slightly older version of Directus locally, but at least in it... (1) Repeaters can't reference collections. If you want to reference other collections, you have to create a relationship (like Many-to-Many). Which is not quite as convenient, but a bit more powerful. (2) As far as I know, nope. For this, you have to manipulate it in Gatsby. I do my manipulation in Elder.JS.