Possible to Store Attachments Elsewhere

[ManelyDave]

Largely as a result of how our team works, our docker implementation blows away the previously running nginx+php server when we deploy to production. The database is separate and on initial startup the container does what needs to happen for it to be fairly seamless. The attachments however are in the filesystem and destroyed.
I've figured that we could have a periodic cron job store attachments onto a separate server that wouldn't be part of the build and some nginx trickery could probably serve up attachments from that. Before I got to work on it, though, I wanted to be sure there's not some magical way to already do this that you've already baked in.

You've really done a great job. I recently migrated our support team off of Salesforce and it's been super. I love what it can do out of the box and love that we've been able to add modules to do business-specific stuff.

[freescout-helpdesk]

There is no such feature for now

[alekseyp]

Using Laravel's filesystem api will open doors to using something like s3:

https://laravel.com/docs/5.5/filesystem

[freescout-helpdesk]

Yes. See https://laravel.com/docs/5.5/filesystem

[ManelyDave]

My co-worker managed to mount an AWS EFS share in the spot in the existing filesystem where Freescout expects all the files to be stored/served from, and that hack seems to be working fine. Thanks!