Creating and understanding Storage buckets

The Supabase Storage service will power any of your Supabase-based applications with whatever file-based feature you can imagine (for example, creating your own Dropbox clone). In our case, we want to use the Storage service to allow attachments in ticket comments for our ticket system.

Before we start with this implementation, I should introduce you to the heart of Supabase storage, buckets. A bucket exists to hold files. Hence, you need at least one bucket to store files.

You can create as many custom-named buckets as you want to have a good separation of concerns. For example, let’s take a production application I worked on in the past. The application was a municipality manager with specific users, internal Dropbox-like file access, and the possibility to post news internally allowing for comments. In this case, I used three buckets – one named avatars for profile pictures, one named intranet for internal file uploads...