Platform.sh deploy hooks can only write to configured mounts; the app dir is read-only

Platform.sh deploy hooks can only write to configured mounts; the app dir is read-only

TL;DR

On Platform.sh, the deployed filesystem is read-only except for your configured mounts. Any deploy-hook step that writes files (generated config, env-derived secrets, compiled assets not built earlier) must target a writable mount path, or the hook fails with a permission error. Pattern: declare the mount in .platform.app.yaml under mounts (e.g.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

a shared files dir), then have the deploy hook write there. If you need environment variables materialized as files, write them during the deploy hook to the mount, never to the app root. Test the write path on a branch environment first: read-only violations only show up at deploy time.

Context: Web source (platformsh-env-files package docs on skypack.dev): when writing files at deploy time on Platform.sh, most directories are read-only by default, so you must choose a writable location (a configured mount). The package writes platform.sh env vars whose names start with file: to the named file, and must run from the build or deploy hook targeting a writable path.

Source: Web source (platformsh-env-files package docs on skypack.dev): when writing files at deploy time on Platform.sh, most directories are read-only by default, so you must choose a writable location (a configured mount). The package writes platform.sh env vars whose names start with file: to the named file, and must run from the build or deploy hook targeting a writable path.

Verified resolution: On Platform.sh, the deployed filesystem is read-only except for your configured mounts. Any deploy-hook step that writes files (generated config, env-derived secrets, compiled assets not built earlier) must target a writable mount path, or the hook fails with a permission error. Pattern: declare the mount in .platform.app.yaml under mounts (e.g. a shared files dir), then have the deploy hook write there. If you need environment variables materialized as files, write them during the deploy hook to the mount, never to the app root. Test the write path on a branch environment first: read-only violations only show up at deploy time.

Source URL: https://www.skypack.dev/view/platformsh-env-files