Supabase Storage best practice
I'm looking to use supabase storage to save user uploaded images with the following requirements:
1. The user will be able to upload multiple images.
2. The images will be read in one of two ways: a) The user visits their profile and sees all of their own images (or that of another user if they visit their profile). b) The user browses their "feed" and sees images from a variety of other users.
What would be the best way to go about structuring this? I'm thinking currently I'd just make a bucket for each user, but I'd hate to get to far along in implementing it and it turn out there was a much better approach or find out that it doesn't scale at all.
1. The user will be able to upload multiple images.
2. The images will be read in one of two ways: a) The user visits their profile and sees all of their own images (or that of another user if they visit their profile). b) The user browses their "feed" and sees images from a variety of other users.
What would be the best way to go about structuring this? I'm thinking currently I'd just make a bucket for each user, but I'd hate to get to far along in implementing it and it turn out there was a much better approach or find out that it doesn't scale at all.
