How to Set Up Supabase Locally Step-by-Step | (Docker + VS Code) | Code Career & Cloud by Mayank 🚀 скачать в хорошем качестве

How to Set Up Supabase Locally Step-by-Step | (Docker + VS Code) | Code Career & Cloud by Mayank 🚀

Welcome back! 👋 In this video, I’ll show you how to set up Supabase locally using VS Code and Docker — the exact same environment the cloud version uses! 🚀 This is a complete walkthrough where you will learn: 🔍 What You’ll Learn ✔ Run Supabase locally using npx supabase start ✔ What Docker services Supabase installs ✔ Explore auto-created supabase folder structure ✔ Understand database migrations & version history ✔ Check services status (Postgres, API, Realtime, Studio) ✔ View configuration in config.toml ✔ How local Supabase mirrors production behavior By the end of this guide, you’ll have your own fully functioning Supabase development setup — perfect for building, testing, and experimenting safely before deploying to cloud. 00:00 – 00:08 “Hey everyone, hope you’re doing well. In this video I’m going to walk you through how to set up Supabase locally and get everything running the right way.” 00:08 – 00:20 “So I already have my project open in VS Code. You can see the folders on the left and the terminal at the bottom. Nothing special here, just a regular setup.” 00:20 – 00:33 “Alright, first step. I’m going to start Supabase using the command, npx supabase start. This basically kicks off the whole local environment.” 00:33 – 01:10 “Now if you’re running this for the first time, you’ll see a bunch of Docker layers getting downloaded. Don’t worry, this is totally normal. Supabase uses different containers for Postgres, the API, the dashboard, and everything else. So it’s just pulling what it needs.” 01:10 – 02:10 “This part can take a little while, depending on your internet speed. Docker is downloading and unpacking each component and getting everything ready so Supabase can run smoothly. You just need to wait for it to finish.” 02:10 – 03:00 “Once all the images are in place, Supabase starts each service one by one. In a moment you’ll see connection details and URLs show up in the terminal. That’s how you know things are coming online.” 03:00 – 03:20 “And right there, you’ll notice a new folder appearing in the project. It’s named supabase.” 03:20 – 04:10 “I’m opening that folder now. Inside it you’ll find migrations, seeds, functions, and a few configuration files. These are the files Supabase uses to track your schema and manage your local setup.” 04:10 – 05:00 “Next, I’m opening the config.toml file. This is basically the heart of your local configuration. Up at the top, you’ll see your project ID and then all the different ports that Supabase uses.” 05:00 – 06:00 “As you scroll through the file, you’ll notice more settings like auth options, storage configuration, JWT details, and other small things. Most people never touch this file, but it’s helpful to know what’s inside.” 06:00 – 07:30 “One of the best things about Supabase is that your local setup behaves just like the cloud version. So whatever you test here should work the same way in production. You can create tables, write SQL, test functions, check authentication, all without deploying anything.” 07:30 – 08:30 “Back in the terminal, you can see that all the services are running. Postgres is active, the API gateway is ready, Realtime is connected, and Studio is available. This means the environment is good to go.” 08:30 – 10:00 “At this point, you can use the Studio dashboard to manage your database visually or connect to the local Postgres instance with any SQL client. Everything is working exactly like a live Supabase project.” 10:00 – 12:00 “The migrations folder will grow over time as you build out your schema. Every change gets saved as a migration, so you can keep your database version controlled. This is super helpful for team projects.” 12:00 – 13:30 “I’m just walking through the folders again so you can see how everything fits together. The functions folder is where you would create your edge functions, and the migrations folder is basically your history of database changes.” 13:30 – 14:10 “Whenever you restart Supabase, it loads everything from these files so your environment stays consistent. That’s why it feels stable and reliable even when you’re switching between different projects.” 14:10 – 14:50 “So that’s pretty much the whole process. Open your project, run the start command, let Docker set everything up, and explore the generated files so you know what’s going on.” 14:50 – 15:01 “Thanks for watching, and hope this helped you get your Supabase setup running. See you in the next one.” If this helped you get Supabase running smoothly — 💬 Drop a comment 👍 Smash the Like button 🔔 Subscribe for more Dev Tutorials! See you in the next one 👋 Hall of the Mountain King by Kevin MacLeod is licensed under a Creative Commons Attribution 4.0 license. https://creativecommons.org/licenses/... 👨‍💻 Subscribe for more:    / @yourchannelhandle   #CodeCareerAndCloud #CodingTips #DevTools #Cloud #AI #Shorts