Strapi on Cloudron — Content-Type Builder Blocked by Read-Only Filesystem

[LoudLemur]

Strapi on Cloudron — Content-Type Builder Blocked by Read-Only Filesystem
Hi all — posting this to save others the troubleshooting time we spent.
We installed the Strapi package on Cloudron and ran into a fundamental blocker: the /app/code directory is read-only, which means Strapi's Content-Type Builder cannot write schema files and is effectively unusable in production mode. The strapi transfer CLI tool also cannot push content types to the destination for the same reason.
We tried mount -o remount,rw, cloudron push, and exec shell workarounds. None work due to how Cloudron isolates app filesystems.

For packagers: Would it be feasible to add a hook in start.sh that copies schema files from /app/data/src/api/ into the build at startup? Something like:
bashif [ -d /app/data/extensions/src/api ]; then
cp -r /app/data/extensions/src/api /app/code/src/api
fi
This would allow users to drop schema files into the persistent data volume and have them picked up on restart, making the package genuinely usable without rebuilding the Docker image.

For users: If you need a Cloudron-hosted CMS with full schema management, Directus (available as an official Cloudron package, v11.16.0) stores its schema in PostgreSQL rather than the filesystem, so it works perfectly within Cloudron's model. We're switching to it.
Thanks to the Cloudron team for a great platform. This is a packaging-level fix rather than a Cloudron core issue.