[CLOSED] How to use different Storage providers for functions?

Im using S3 as Appwrite Self-Hosted Storage, and now all builds are there. Can i use S3 only for Upload Files Buckets, and keep Builds and Functions locally?

TL;DR

The user wants to use different storage providers for different purposes: S3 for storage/uploads, and local storage for builds and deploys. It is stated that this may not be possible with Appwrite's current setup. The suggested solution is to customize the `init.php` file to modify the logic of the `getDevice` function. However, a possible workaround is provided: setting `_APP_STORAGE_DEVICE` as `s3` in the Appwrite configuration and filling in the S3 fields. This will allow S3 to be used for storage/uploads, as well as for functions builds and deploys. The cache, config, and certificates

First, you can use S3 for Appwrite by setting _APP_STORAGE_DEVICE as s3 and filling all the S3 fields

TypeScript

_APP_STORAGE_DEVICE=s3
_APP_STORAGE_S3_ACCESS_KEY=
_APP_STORAGE_S3_SECRET=
_APP_STORAGE_S3_REGION=us-east-1
_APP_STORAGE_S3_BUCKET=

Second, this will be in use for:

Storage / Uploads
Functions builds
Functions deploys

The cache (half-way) & config & certificates will remain local

Can i split like this?

Storage / Uploads - Local
Functions builds - S3
Functions deploys - S3

It won't work 😦

You can see here that Appwrite is getting the device for each of those three here using the getDevice function https://github.com/appwrite/appwrite/blob/master/app/init.php#L976-L986

That function is declared here https://github.com/appwrite/appwrite/blob/master/app/init.php#L988 And you can see that all called to this device will be treated the same.

If you want to avoid this you'll need to customize the init.php file of your Appwrite container changing the logic of getDevice function.

TY .. Close

This can be a possible feature request