Delv
Supabase
Getting Started Guide

How to Use Supabase

A practical guide to get you up and running with Supabase. Written by Delv Editorial, Delv Team.

Getting started with Supabase

After reading this guide, you'll know how to set up your Supabase account, create a database, and manage user authentication and storage quickly. You'll be ready to build applications using a powerful backend in just a few minutes.

Step 1: Sign up and set up

  1. Go to supabase.com.
  2. Click on the "Start your project" button in the top right corner.
  3. Sign up using your email or GitHub account.
  4. Once logged in, click on "New Project."
  5. Fill in the project details: name, password, and select a region. Note that your database will be free for up to 500MB.
  6. Click "Create new project" to set up your database.

Step 2: Your first database table

  1. In your project dashboard, navigate to the "Table Editor" from the left sidebar.
  2. Click "Create a new table."
  3. Name your table (e.g., "Users") and define the columns (e.g., id as integer, name as text, email as text).
  4. Check the "id" column as the primary key and click "Save" to create the table.
  5. To insert data, go to "Table Editor," select your table, and click on "Insert Row." Fill in the fields and click "Save."

Step 3: Get better results

  1. To manage user authentication, navigate to "Authentication" in the sidebar.
  2. Under "Settings," configure your email templates for sign-up and password recovery.
  3. To enable file storage, go to "Storage" and create a new bucket for your files.
  4. Use the API documentation available in the "API" section for integrating your frontend with the Supabase backend efficiently.

Pro tip

When creating your database tables, use the "Insert Row" feature to quickly populate your tables with sample data. This helps you test your application without needing to write any SQL.

Common mistake to avoid

Do not forget to set the primary key for your tables. Failing to do this can lead to issues with data integrity and difficulties when querying your data later. Always ensure each table has a unique identifier.