Back
Understanding S3 setup with appwrite
Hey, i'm planning to change the storage from local to S3, tho i have some questions to see before starting the migration.
- Does all the
/storage/<storage_type>will be migrated to S3 ? - How does the S3 path looks like ? is it like
<bucket>/<storage_type>/<files>or something else ? (since the getDevice root isAPP_STORAGE_UPLOADS = '/storage/uploads'could it be<bucket>/storage/<storage_type>/<files>?) - Do you use ACL requests ? since i'm planning to use garageHQ, they don't have ACL/Policies endpoints (see https://garagehq.deuxfleurs.fr/documentation/reference-manual/s3-compatibility/)
- Do you use public facing object ? or for public / get objects you use a presign ? as garage don't allow public access for now, but allow presign requests
TL;DR
- Developer wants to switch storage from local to S3 in Appwrite.
- Questions about migration:
1. Will all '/storage/<storage_type>' content be migrated to S3?
2. How does the S3 path look like?
3. Do they use ACL requests? Planning to use garageHQ.
4. Do they use public facing object or presign requests for public/get objects?
Solution: Open-source MinIO deprecated, suggests using AlStor instead for S3.also, i don't use minio because the opensource part is now deprecated, and they want us to use AlStor instead
