Potentional Local Storage Bug on Self-Hosted Supabase? Partly file upload.
Hi,
1. I have changed setting in docker-compose.yml so instead on S3 to upload locally.
2. Login to Supabase Studio, go to Storage, Created Bucket, Folder and tried to upload file using Supabase Studio.
3. After finishing this file was not listed in the folder on Supabase Studio. I try to find its location with console and find out that it was created folder with this filename(6.jpeg) and inside was two files:
- 45766fe7-40ff-4c32-bcd9-196861002abd which need to be uploaded image and
- 45766fe7-40ff-4c32-bcd9-196861002abd.json
4. File that need to be image itself is 0 bytes.
5. In .json file have this info
1. I have changed setting in docker-compose.yml so instead on S3 to upload locally.
2. Login to Supabase Studio, go to Storage, Created Bucket, Folder and tried to upload file using Supabase Studio.
3. After finishing this file was not listed in the folder on Supabase Studio. I try to find its location with console and find out that it was created folder with this filename(6.jpeg) and inside was two files:
- 45766fe7-40ff-4c32-bcd9-196861002abd which need to be uploaded image and
- 45766fe7-40ff-4c32-bcd9-196861002abd.json
4. File that need to be image itself is 0 bytes.
5. In .json file have this info
