Right now we can define the themes path as a s3 bucket, and it will load the assets from the s3, but when editing a content via the backend, the results are saved locally. I dug a little, and found that the themes path is tried to be set on the RegisterOctober.php file via a config item called "cms.themesPathLocal" (which apparently doesn't exists) instead of the cms.themesPath item. Changing this item breaks the app, so i guess that's not the way it's intended to work. As the themes path is not set, the application takes the basePath and appends "themes" to create the themes path.

Is there any way to do this right now, or would it require some modifications to the core?

Hi there, just a quick check. I am having the same problem as well. Do you manage to find the solution for this?

You may want to look into mounting an s3 bucket / prefix to the themes directory and use s3 as a "file system".

Worked for me using Goofys / FUSE.

Good idea

h said:

You may want to look into mounting an s3 bucket / prefix to the themes directory and use s3 as a "file system".

Worked for me using Goofys / FUSE.

Last updated 6 years ago

@ariponce Additionally, the themesPathLocal should be a local path on your container, and not a public relative path.

So on a server it could be set in config/cms.php to something like:

'themesPathLocal' => '/var/www/example.com/[new themes directory]',