cli VS supabase

Recently, I noticed that in our remote project, the database storage schema has a migration not present when one sets up the local stack for development. Upon inspection, the Supabase CLI uses an old version of the storage image. Currently, there is no way to change this (that I know of) until the CLI team updates the CLI to use this version.

@doganugurlu Looks like Deno team implemented a fix https://denostatus.com/cllm0jzq219036bjottk03k2ac Are you still experiencing the issue?

We used to cache the modules locally, I will need to check if we made any configuration change. Can you kindly open an issue for Supabase CLI - https://github.com/supabase/cli/issues

> Oh, I had no idea that the functions routes were "wild card"! I don't think that's mentioned anywhere in the documentation, btw.

Good point! will update the docs.

> Sorry, I actually mean "import-maps": https://github.com/supabase/cli/issues/1338

I'll take a look at this issue. We've improved import map resolution in the last couple of CLI releases. But it looks like there are more edge cases.

We’ve moved the Supabase CLI to a fortnightly stable-release cycle. Every 2 weeks, we will update the latest tag on npm, the supabase/tap for homebrew, and the supabase scoop bucket. You can find the binary downloads in our GitHub latest release.

I think we've been working on that recently here: https://github.com/supabase/cli/pull/907

Can you try it locally with the supabase CLI? https://github.com/supabase/cli

For more info see this issue on GitHub.

I opened a Github issue: https://github.com/supabase/cli/issues/939, but I figured I'd see if any of you hit this and, hopefully, got past it.

Are there plans to support connections to self hosted remotes (to deploy to self-hosted instances, for example) with the cli? https://github.com/supabase/cli/issues/753

The errors you cite come from the https://github.com/supabase/cli not from postgREST(it does support v15).

Semantic search demo

1. Create a new Supabase project: Visit Supabase and create a new project.

Supabase positions itself as the "open source Firebase alternative." It was founded in 2020 and is a developer-friendly serverless database platform that supports over 20 frameworks, including popular tools like Next.js, React, Nuxt, Svelte, Flutter, and Vue.

You can find the full application code as a Python Poetry project on GitHub.

If you use PostgreSQL and are proficient with using its row-level security feature, you can choose from several tools/services built above RLS, including Supabase, PostgREST, and PostGraphile. They all provide a way to expose database CRUD as a web API, assuming you've configured the RLS rules to properly secure the access.

Here the thing that accelerated my development the most: Supabase. Thanks to its Database, Authentication, and Edge Functions, we were able to rapidly develop the app. Their JS library made development super seamless, and their local development stack made testing a breeze.

On certain databases, yes

We only scanned for firestore, which is a NoSQL database, conversion tools may still be possible, a good firebase alternative would be https://supabase.com, but please set up RLS, its IMO much easier then Firebase.

Supabase - PostgreSQL

I am working on a Supabase project that is going to have a data model that supports content (called nuggets) that can belong to either users individually or to teams.

Supabase as our DB