I added an option to include an external storage (smb/cifs) via env vars.
limitations:
only one external storage folder
password must be in env (couldn't think of a way to access docker secrets when creating volumes; would recommend to use git crypt if you have user has env in repository)
Tried to create the upload-folder like this as well, but this didn't work, I think because immich expects it to have already a folder and file structure.
if anyone has ideas on how to improve this before (or after) publishing, I'm glad to discuss :)
I added an option to include an external storage (smb/cifs) via env vars.
limitations:
- only one external storage folder
- password must be in env (couldn't think of a way to access docker secrets when creating volumes; would recommend to use `git crypt` if you have user has env in repository)
Tried to create the upload-folder like this as well, but this didn't work, I think because immich expects it to have already a folder and file structure.
if anyone has ideas on how to improve this before (or after) publishing, I'm glad to discuss :)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I added an option to include an external storage (smb/cifs) via env vars.
limitations:
git cryptif you have user has env in repository)Tried to create the upload-folder like this as well, but this didn't work, I think because immich expects it to have already a folder and file structure.
if anyone has ideas on how to improve this before (or after) publishing, I'm glad to discuss :)
as it's deploying successfully and not interfering with the original recipe, I will merge it now