Move file in directus app: read-only file system

[devtron]

I can't apply my scheme to directus:

root@...:/app/data# npx directus schema apply snapshot.yaml 
npm ERR! code EROFS
npm ERR! syscall open
npm ERR! path /root/.npm/_cacache/tmp/e889ceb7
npm ERR! errno EROFS
npm ERR! rofs Invalid response body while trying to fetch https://registry.npmjs.org/directus: EROFS: read-only file system, open '/root/.npm/_cacache/tmp/e889ceb7'
npm ERR! rofs Often virtualized file systems, or other file systems
npm ERR! rofs that don't support symlinks, give this error.

[devtron]

Still have this issue...

[nebulon]

@devtron on Cloudron all apps run in a read-only filesystem, causing this issue. However for things which need to be writeable, we link them into to the read/write section.
What is the use-case, requiring you to move the snapshot.yaml ?

[devtron]

@nebulon The use-case is to import my schema (snapshot.yaml) from my local development into the prod environment (cloudron app instance). And vice versa.
In fact, I need to import into the app only once, because I already created my schema locally. It would be tedious to define everything in the app again.

[MooCloud_Matt]

@devtron
I think that was a feature in version 8 or lower but is really interesting if it's still supported, can post the link to the documentation.

[devtron]

@moocloud_matt
Here is the link for their newest version 9
https://docs.directus.io/reference/cli/#snapshot-the-data-model

I am also using Directus 9 and used it during their rc-phase

[MooCloud_Matt]

@devtron
Nice, the old version has a dedicated page on it, and I didn't find it on the new documentation.

[nebulon]

@devtron said in Move file in directus app: read-only file system:

@nebulon The use-case is to import my schema (snapshot.yaml) from my local development into the prod environment (cloudron app instance). And vice versa.
In fact, I need to import into the app only once, because I already created my schema locally. It would be tedious to define everything in the app again.

ah I see, if this is a one-time task, you could also put the app in debug mode, which makes the filesystems temporarily read/write (but not persistent across restarts)

[devtron]

@nebulon I put the app in recovery/debug mode. It became writable but got another issue:

"DB_CLIENT" Environment Variable is missing.

I've tried to add the changes in the env file in app/data. It didn't work. After that I tried to start it normally and got a new error with redis:

[nebulon]

@devtron the DB_CLIENT is set and configured in the /app/pkg/start.sh which also sets up other required settings. So while having the app in debug mode, you either have to run relevant pre-setup commands required for npx directus schema apply or put that line at the correct place in /app/pkg/start.sh and run that whole script.

For redis, you can check the services view in your dashboard and manually start it from there first.

[devtron]

@nebulon Alright, got it. Thank you!