Custom file storage path

Infos:

  • Used Zammad version: 5.1.x
  • Used Zammad installation type: package
  • Operating system: Centos 7.9
  • Browser + version: Edge Version 100.0.1185.50

Expected behavior:

  • Is there a environment setting to change the attachment storage path?

Actual behavior:

  • could not find in docs

Steps to reproduce the behavior:

  • I’ve been using Zammad for more than 1 year and it is really working well! My team loves it so much! Thanks very much to Zammad team.

My initial setup is in 4C 8G 100G VPS. After one year, the storage of attachment is about 60G. I think it is better to get another cloud disk to store the attachment so that the system could have enough space for the other work. Wonder if it is an environment setting for this? Will Zammad support S3 in the near future?

Thanks again Zamma team for doing an awesome job!

I fixed it after searching around. I subscribed a NAS and mounted it to my server at /mnt/nas. Then copy all the files from /opt/zammad/storage/fs to /mnt/nas. Because I am not able to tell Zammad to change the storage file system path, I used the soft link to

ln -s /mnt/nas /opt/zammad/storage/fs

Please note that above solution may cause issues with upgrade or backup scripts.
If you use that solution, double check everything in above mentioned scenarious as changing the path currently is not supported officially by Zammad.