Open richard-aio opened 3 years ago
I can see the issue is that "s3" is hard coded in the solution as the disk name, instead of using the configuration for the disk driver.
If I get time over the next few days I will submit a pull request to resolve the issue.
When streaming the response from an S3 instance (DigitalOcean Spaces, using S3 driver), the disk is ignored and FileValue attempts to ready directly from the local disk:
As you can see in the log file, FileVault is using fopen() in my local directory: