Repository navigation
Chamilo 3.0.2 – How to change where var/upload is stored (another disk or S3)? Hardcoded paths in the code #9433
Replies: 1 comment
|
For the local-disk move in 3.0.2, preserve the path Chamilo currently expects: mount/bind-mount the new The versioned local adapters For that migration:
Treat S3 as a separate migration. An S3 adapter does not make direct local-file operations use object These references are pinned to v3.0.2. I cannot identify a release fixing every listed path or certify |
Uh oh!
There was an error while loading. Please reload this page.
Hi. We run Chamilo 3.0.2 and would like
to know the correct way to change where uploaded files are stored.
I have read admin-guide/installation/cloud-storage.md and the comments in .env.dist
(lines 109-114), but I still have these questions:
Moving to another folder or disk while staying on local storage.
Is the right way to change the "location" of the adapters in config/packages/oneup_flysystem.yaml
(for example resource_adapter, line 46), or to mount the new disk (or a symlink) at var/upload
without touching the configuration?
Hardcoded paths.
In 3.0.2, several parts of the code build kernel.project_dir.'/var/upload/resource'
directly, without going through the Flysystem filesystem. For example:
If resource_adapter is switched to *_awss3_adapter (or its "location" is changed), do these
features stop working? Is this a known issue? Is there an issue or a release where it is fixed?
Is S3/Azure/GCS storage considered production-ready in 3.0.x?
If we move to S3, what exactly needs to be copied?
All of var/upload, or only var/upload/resource and var/upload/assets? What about
var/upload/course_legal and var/upload/users, which are not Flysystem filestores?
Differences between the 3.x documentation and 3.0.2:
From which version do these apply?
Thanks.
All reactions