Read This Or Get Confused

Recap

What You'll Learn Today

Who's. That. Instructor!?

What Is Supabase?

Supabase > Firebase

How To Connect Bolt With Supabase

Adding Authentication

How To Make Bolt Use 5x Fewer Tokens & Execute 5x Faster

How To Debug Your App

Introduction

Continuation of Overnight Fullastack Applications - This workshop recording will show you how to connect your Bolt applications with Supabase, how to create your first few tables, and how to debug your app when it inevitably crashes.

All in less than an hour so you can go and implement everything immediately after

How To Connect, Code & Debug Supabase With Bolt

**What is Supabase** and why it pairs perfectly with Bolt

Are you burning your money by using Firebase?

**Live Debugging** and why you can't trust the machine

**How to make Bolt run 5x faster and use 5x less tokens** with a single prompt

 All right, so now let's add, let's remove the dummy data from the client, from the front, from the front end, and add it to the database.

Create menu items and connect them to the shop and the user that is logged in.

Because every shop would have its own items and its own categories. That's why we would connect every item with every user. I mean, every user would have their own items instead of everyone having the same items. Of course, if you build it into an acutal app and scale it, you might have some default items.

You can just immediately pop into each user's database to have them, because pretty much everyone will have a plain bagel. Pretty much everyone will have water to sell, so you could just give them all those kind of items to them immediately, and then have them interact with their menu add items, remove items, change prices, or whatever.

It's already done. Apply changes. So what did we do? We treat new menu items, stable shop menu items. Menu items to source with custom pricing policies. We use String IDs instead of numbers.

And we have component load menu new. Alright, let's see. Now we have example dot com and the password and sign in. Now I don't have any items, of course.

Also, actually, let's look into our Supabase account.

When you sign up you have to create an organization, I have already created mine and if I go to my projects, you can see this Super Based Bagel Shop POS. Let me refresh actually for good measure. And here we are. And now if we go to our database, this is a schema visualizer with the users,

shop name and created_at And where in what are our,

I don't see our menu items for some reason.

Let's see this. Okay. Ignore because we've already solved that.

Maybe if I refresh, it'll be here, but maybe not. And yeah, it's not here yet. Let's try and create a screen where we can add and remove menu items. And maybe when we do that it will actually go create the tables still. If not, we can just prompt it to create the tables just by itself. Let's add screen where I can add slash edit slash delete Menu items .

And now we're getting a menu management screen. That's a new one I think.

Uh. We are pretty much ready. We just need to re paste the app.tsx file to have the updated header.

And we'll be done in just like couple of minutes. Actually less than couple minutes, maybe a minute until the app loads

Alright we've added them menu management, screen, the menu items, updated prices Toggle items active or inactive and new items for the available menu items. Alright, so let's log in and check it out.

Doesn't even show me anything. The menu failed to load available items. Okay. Because probably because the table does not exist or because we don't have any items right now.

Let's see. Yeah, I think it just forgot to create the tables actually on the database and just take the migration files that include the tables, but somewhere along the way it got lost.

Yeah, exactly. As we said, it hasn't created the necessary tables and relationships.

and there's another problem right now. Okay?

It is the same as before, so let's just try to fix it.

Basically, we're trying to add a rule that we already have, and that's why it doesn't let us add the rule because it's already there.

Okay, now we try to create the table with the price not being able to be null, but because we have no menu items, it has no values, probably because we already have our users in our shop somehow try to create a row or something that had no values in it because there are no menu items

unless it was station one, duplicate key value

  Again, because it's just reapplying the migration files. It just tries to add the same rules over and over. And this is an issue that hopefully Supabase will be able to fix soon. As you'll see after we get a bit of this, but

Okay, so again, it's the same thing that we already have the rule.

Let's see what would happen if we actually try to access our, uh, go to the menu and add the item. So select an item, right? Plain bagel, and enter a price, $2 and add an item. And it failed to load the item for some reason... which I don't know why

failed to add the item when I clicked on add item.

Let's see what the issue is. Probably again something about the rules.

---
title: How To Debug Your App
isPublicLesson: true
privateVideoUrl: https://stream.mux.com/i3MvD8kmxQO991kw00MnIOhFb1o70202YLBrEPQjveVgJc.m3u8
---

 All right, so now let's add, let's remove the dummy data from the client, from the front, from the front end, and add it to the database.

Create menu items and connect them to the shop and the user that is logged in.

Because every shop would have its own items and its own categories. That's why we would connect every item with every user. I mean, every user would have their own items instead of everyone having the same items. Of course, if you build it into an acutal app and scale it, you might have some default items.

You can just immediately pop into each user's database to have them, because pretty much everyone will have a plain bagel. Pretty much everyone will have water to sell, so you could just give them all those kind of items to them immediately, and then have them interact with their menu add items, remove items, change prices, or whatever.

It's already done. Apply changes. So what did we do? We treat new menu items, stable shop menu items. Menu items to source with custom pricing policies. We use String IDs instead of numbers.

And we have component load menu new. Alright, let's see. Now we have example dot com and the password and sign in. Now I don't have any items, of course.

Also, actually, let's look into our Supabase account.

When you sign up you have to create an organization, I have already created mine and if I go to my projects, you can see this Super Based Bagel Shop POS. Let me refresh actually for good measure. And here we are. And now if we go to our database, this is a schema visualizer with the users,

shop name and created_at And where in what are our,

I don't see our menu items for some reason.

Let's see this. Okay. Ignore because we've already solved that.

Maybe if I refresh, it'll be here, but maybe not. And yeah, it's not here yet. Let's try and create a screen where we can add and remove menu items. And maybe when we do that it will actually go create the tables still. If not, we can just prompt it to create the tables just by itself. Let's add screen where I can add slash edit slash delete Menu items .

And now we're getting a menu management screen. That's a new one I think.

Uh. We are pretty much ready. We just need to re paste the app.tsx file to have the updated header.

And we'll be done in just like couple of minutes. Actually less than couple minutes, maybe a minute until the app loads

Alright we've added them menu management, screen, the menu items, updated prices Toggle items active or inactive and new items for the available menu items. Alright, so let's log in and check it out.

Alright? Okay, now what is the error?

Doesn't even show me anything. The menu failed to load available items. Okay. Because probably because the table does not exist or because we don't have any items right now.

Let's see. Yeah, I think it just forgot to create the tables actually on the database and just take the migration files that include the tables, but somewhere along the way it got lost.

Yeah, exactly. As we said, it hasn't created the necessary tables and relationships.

Alright, let's apply the changes

and there's another problem right now. Okay?

It is the same as before, so let's just try to fix it.

Basically, we're trying to add a rule that we already have, and that's why it doesn't let us add the rule because it's already there.

Okay?

_pure gibberish_. 

Okay, now we try to create the table with the price not being able to be null, but because we have no menu items, it has no values, probably because we already have our users in our shop somehow try to create a row or something that had no values in it because there are no menu items

unless it was station one, duplicate key value

  Again, because it's just reapplying the migration files. It just tries to add the same rules over and over. And this is an issue that hopefully Supabase will be able to fix soon. As you'll see after we get a bit of this, but