ARK

Running the Database Schema

Your ARK product needs database tables before it can store anything. Each ARK repo includes a schema.sql file that creates every table, relationship, and security rule the product needs. You'll paste this file into the Supabase SQL Editor and click Run.

One minute.

1. Find the schema file in your repo

Your ARK repo (the one in arkteams/<product>-xxxxxx) has a file at the top level called schema.sql. Open it in your browser:

  1. Go to your repo on GitHub (e.g., https://github.com/arkteams/track-a1b2c3).
  2. Click the file schema.sql in the file list.
  3. Click the Raw button (top right of the file view) — this shows the file as plain text.
  4. Select all the text (Cmd+A on Mac, Ctrl+A on Windows).
  5. Copy it (Cmd+C / Ctrl+C).

Keep this tab open in case you need to copy it again.

2. Open the SQL Editor in Supabase

  1. Open your Supabase project tab (or go to supabase.com → your project).
  2. In the left sidebar, click the SQL Editor icon (it looks like a database with >_ next to it, near the middle of the sidebar).
  3. You'll see a large code editing area. If there's a tab called "Welcome" with sample queries, ignore it.
  4. Click + New query at the top of the editor (or the + tab if you already have queries open).

3. Paste and run the schema

  1. Click anywhere in the empty editor area.
  2. Paste your schema (Cmd+V / Ctrl+V). You should see the SQL text fill the editor.
  3. Click the green Run button at the bottom right (or press Cmd+Enter / Ctrl+Enter).

Supabase runs the entire script. It usually takes 1–3 seconds.

4. Confirm it worked

You should see:

  • A green Success message at the bottom of the editor.
  • Or a results panel showing No rows returned — that's normal for schema scripts; they create tables but don't return data.

To double-check:

  1. In the left sidebar, click the Table Editor icon (looks like a spreadsheet, above the SQL Editor icon).
  2. You should now see a list of tables in the left panel: things like profiles, boards, contacts, etc. The exact table list depends on which ARK product you're installing.

If you see tables, you're done with this page. Reload your Vercel URL — the "missing tables" error should be gone.

Next: Your First Login

Troubleshooting

"permission denied for schema public"

You're probably running the schema as a regular user instead of using the SQL Editor. The Supabase SQL Editor runs queries as the project owner with full permissions. Make sure you're using the SQL Editor in the Supabase dashboard, not connecting through a separate tool like psql.

"relation already exists"

You've already run the schema once. The error is harmless — it means the tables you tried to create are already there. You can ignore it and move on. If you want a clean slate, see the next troubleshooting entry.

"I want to start over"

To wipe the database and start fresh:

  1. SQL Editor → New query.
  2. Paste: 
    drop schema public cascade;
create schema public;
grant all on schema public to postgres;
grant all on schema public to public;
  3. Click Run. This deletes everything.
  4. Now paste your schema.sql and run it again.

"syntax error at or near ..."

You may have copied the schema with formatting (HTML tags, line numbers, etc.). Go back to GitHub, click the Raw button (top right of the file view), and copy from there. The Raw view is plain text with no formatting.

"I see the schema ran but my product still shows errors"

Make sure you copied the Project URL and anon key correctly into Vercel. A typo in either one means the website connects to a nonexistent project (or an empty one). See the Verify Your Deployment page for the full checklist.