Skip to content

Commit 9f8c6f8

Browse files
Merge pull request #50 from eltociear/patch-1
2 parents 7fef4fa + 0241304 commit 9f8c6f8

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/getting_started.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ We will use Supabase as our database (with vector search, pgvector), authenticat
5656

5757
9. Install Supabase and set up the CLI. You should follow thier [guide here](https://supabase.com/../guides/cli/getting-started?platform=macos#installing-the-supabase-cli), but in short:
5858
- run `brew install supabase/tap/supabase` to install the CLI (or [check other options](https://supabase.com/../guides/cli/getting-started))
59-
- Install [Docker Desktop](https://www.docker.com/products/docker-desktop/) on your computer (we won't use it, we just need docker dameon to run in the background for deploying supabase functions)
59+
- Install [Docker Desktop](https://www.docker.com/products/docker-desktop/) on your computer (we won't use it, we just need docker daemon to run in the background for deploying supabase functions)
6060
10. Now when we have the CLI, we need to login with oour Supabase account, running `supabase login` - this should pop up a browser window, which should prompt you through the auth
6161
11. And link our Supabase CLI to a specific project, our newly created one, by running `supabase link --project-ref <your-project-id>` (you can check what the project id is from the Supabase web UI, or by running `supabase projects list`, and it will be under "reference id") - you can skip (enter) the database password, it's not needed.
6262
12. Now let's deploy our functions! ([see guide for more details](https://supabase.com/../guides/functions/deploy)) `supabase functions deploy --no-verify-jwt` (see [issue re:security](https://github.com/adamcohenhillel/AdDeus/issues/3))

0 commit comments

Comments
 (0)