Private files setup - #401
Conversation
3a65ba4 to
97629f0
Compare
| phpfpm: | ||
| volumes: | ||
| - ../../shared/${SUB_SITE_FOLDER}:/app/web/sites/${SUB_SITE_FOLDER} | ||
| - ../../shared/private-files:/app/private-files |
There was a problem hiding this comment.
Should this be
| - ../../shared/private-files:/app/private-files | |
| - ../../shared/${SUB_SITE_FOLDER}/private-files:/app/private-files |
?
There was a problem hiding this comment.
I don't know enough about how Drupal manages private files to answer authoritatively, but I would think (hope) Drupal can handle both.
But server side it would probably be an advantage to have the files clearly scoped by sub site in the filesystem. For cleanup, backup and monitoring disk usage.
There was a problem hiding this comment.
Second question is how we migrate existing files if we implement this?
There was a problem hiding this comment.
@turegjorup, there will be some manualt migration steps if we implement this. However, the reason for us having the “sub-site folder” is that we previously1 hosted Loop as a “multisite” (https://www.drupal.org/docs/getting-started/multisite-drupal/set-up-a-multisite) solution (with shared Drupal core). Today, we host Loop as three separate solutions, but still have the sub-site folder because it is (was?) almost impossible to unwrangle, i.e. switch from using web/sites/loop.sundhedogomsorg.dk to web/sites/default as the site folder.
What I'm trying to say is that – on second thought – we probably don't need this.
Footnotes
-
A very, very long time ago … ↩
3 participants
Link to ticket
https://leantime.itkdev.dk/_#/tickets/showTicket/8147
Description
Adds private files setup.
Important
We must manually create the
…/shared/private-filesdirectory before deploying this.