To answer both of your questions simply given all the chaos of previous chatter: The recommended ap
To answer both of your questions simply given all the chaos of previous chatter:
The recommended approach is a single bucket for many users but a single purpose. For example maybe you have a bucket called uploads, and a bucket called avatars. Though you could of course just use one bucket for an entire application if you wanted. Generally most people will recommend a file name structure of
As far as the dashboard showing "folders" there's no actual concept of folders in S3/R2. The dashboard only shows in the way by splitting file names on a slash character if you use one. (So you will actually needs files inside the bucket for it to show a "folder" in the dashboard)
Lmk if you have any other questions
The recommended approach is a single bucket for many users but a single purpose. For example maybe you have a bucket called uploads, and a bucket called avatars. Though you could of course just use one bucket for an entire application if you wanted. Generally most people will recommend a file name structure of
{userId}/{fileId}.extAs far as the dashboard showing "folders" there's no actual concept of folders in S3/R2. The dashboard only shows in the way by splitting file names on a slash character if you use one. (So you will actually needs files inside the bucket for it to show a "folder" in the dashboard)
Lmk if you have any other questions
