I think @james has been researching on the scope of the changes. AFAIK, the main blocker is SSO stops working now. So, maybe we need instructions on how to migrate from SSO to normal login. Also, from your 3rd link maybe it's just a matter of getting a license from them to get OIDC to work. [image: 2c3fc0f4-dece-4659-b929-1daad8f3e170-image.jpeg]

Hello @Mario-0 No problem, always happy to help.

Use the connection string with your MS-SQL server details to connect to the existing database.

@jdaviescoates correct

Closed due to inactivity

Closed due to inactivity

Hi @james . Haven't encountered the issue in a while now, also because that particular Directus app is not in use anymore.

I was digging deeper and found this article in the docs giving closure! So the correct env vars are: export CONTENT_SECURITY_POLICY_DIRECTIVES__FRAME_SRC="array:'self',http://localhost:3000" export CONTENT_SECURITY_POLICY_DIRECTIVES__CONNECT_SRC="array:'self',http://localhost:3000,ws://localhost:3000" export CONTENT_SECURITY_POLICY_DIRECTIVES__SCRIPT_SRC="array:'self','unsafe-inline'" export CONTENT_SECURITY_POLICY_DIRECTIVES__STYLE_SRC="array:'self','unsafe-inline'" Or specifically adjusted to your use case.

thanks for reporting, made an internal task

@markjames said in Directus not updating to latest version: When I hit update it says 8.0.3 is pre release, use at my own risk. Yes, please update. 8.0.3 is quite old by now, the latest is in fact 8.3.0 (which is being rolled out).

@joseph i firstly created a new template extension folder then run "npm run build" locally and uploaded the package.json file and the folder "dist" in my manually created folder named "directus-extension-helloworld" and goes at my endpoint "https://directus.mydomain.com/helloworld" there it gives the expected response.

I too have done exactly like this but the response is still "{"errors":[{"message":"Route /helloworld doesn't exist.","extensions":{"path":"/helloworld","code":"ROUTE_NOT_FOUND"}}]}" any idea why

Also fixed up the docs at https://docs.cloudron.io/apps/directus/ then

I have been able to find a turnaround for exporting the schema using Node.js. =========== To export your schema from a Directus instance using Node.js Prerequisites Node.js Installed: Ensure Node.js is installed on your system. Directus Instance and Token: Obtain your source Directus project URL and access token. Steps to Export the Schema Setup Node.js Project: Create a new directory and initialize a Node.js project:mkdir directus-schema-export cd directus-schema-export npm init -y Install the required package:npm install cross-fetch Create the Script: Create a file, e.g., export-schema.js, and add the following code: const fetch = require('cross-fetch'); // Replace with your actual Directus project URL and access token const SOURCE_URL = 'https://your-directus-instance.com'; // Your Directus URL const SOURCE_TOKEN = 'your-access-token'; // Your Directus access token async function exportSchema() { try { const response = await fetch(`${SOURCE_URL}/schema/snapshot?access_token=${SOURCE_TOKEN}`); if (!response.ok) { throw new Error(`Failed to fetch schema: ${response.statusText}`); } const { data } = await response.json(); console.log('Schema exported successfully:', data); return data; } catch (error) { console.error('Error exporting schema:', error.message); } } // Call the function exportSchema(); Run the Script: Execute the script using Node.js:node export-schema.js The schema will be logged to the console. You can redirect it to a file:node export-schema.js > schema.json

oh glad it worked out in the end.

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