-
-
@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 ? -
@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
Here is the link for their newest version 9
https://docs.directus.io/reference/cli/#snapshot-the-data-modelI am also using Directus 9 and used it during their rc-phase
-
@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)
-
@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:
-
@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 fornpx 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.