Supabase is an open source Firebase alternative. Start your project with a Postgres database, Authentication, instant APIs, Edge Functions, Realtime subscriptions, and Storage.

Supabase

Hey yall, noob question here - can someone help me understand **why** these async functions are written in two different notations in the Supabase Sveltekit quickstart tutorial https://supabase.com/docs/guides/with-sveltekit
```
const handleLogin = async () => {
    try {
      ...
    } catch (error) {
      ...
    } finally {
      ...
    }
  }
```
VS
```
async function signOut() {
    try {
      ...
    } catch (error) {
      ...
    } finally {
      ...
    }
  }
```

That's basically the same, it just depends of which way you prefer

<@265271986832408588>  I think if you need a reference to "this" in the context you're within, you should use the 2nd one.  I recently just learned, because I was trying to understand how pinia (state management in vue 3) works.  And they *encourage* the usage of arrow functions for getters because it encapsulates from having access to 'this' so state is protected from being mutated.

Thank you that helps! Further reading: https://medium.com/geekculture/regular-vs-arrow-function-1f8140fbcece

are the docs meant to be entirely in serif

on my mac it uses san francisco despite also being unset

Is there a way to serve html from supabase?

In general no.  Supabase is very cautious on anything that can be used to host websites.

It's just that I only need a crud so supabase literally is all I need for backend

Towards the bottom of this edge function blog post is the reasoning... https://supabase.com/blog/supabase-edge-functions
I've seen similar comments on storage.

Perhaps in the future for the enterprise tier

Or maybe an admin panel? That's what I really need

Asked in help and made a suggestion, but just curious if anyone has used a read replica and basically layered all the good things about supabase on top of an existing postgres setup

My guess would be if no one replied in help then no one has done this before. Everyone in <#839993398554656831> is also in <#1006358244786196510> so no need to cross-post.

I've noticed a lack of deference to people trying to find information about Supabase because the docs are seriously lacking. Thanks anyways

Seriously lacking isn't constructive feedback. I'm open to hear what you think is lacking and how it could be improved.

Sure. I think it's more of a mentality that "we're the firebase alternative" and not "we're a configurable database platform you build on". The docs structure is mainly focused on the client landing areas of how you would expect to use supabase in client code, but not on the pieces that compose Supabase. Generally I feel that the docs are great from a 30,000ft view and great from a marketing standpoint, but because there's no deep dive of technical details I'm really lost beyond any greenfield project without having to jump into github and make some assumptions.

The Realtime area is a good example where it feels like a high-level view, more of a footnote in the docs but is itself an entire repository and a pretty deep rabbit hole.

I think the migration area is another telling area where it assumes people are migrating mainly from Firebase into Supabase. If you all are assuming people understand the value of a relational model you can probably assume there's a lot of people who have relational workloads already running and would like to use features of Supabase to add value to existing setups.

As it stands though it's feels like the time I'm spending standing up areas of supabase and poking around is very imbalanced to the time I'm reading in the docs. Given the age/maturity of Supabase, I don't think it's fair to compare to something like Twilio which is more consumer driven or even Postgres docs. In those systems though,  if something is unclear I know how I would look through the docs to come to a conclusion or understanding. Alternatively, if I have implementation that is non-standard I would know how to hunt through those docs to understand the pieces of how an implementation might work.

I really appreciate this feedback and will pass it on to the docs team so we can improve on these as we grow.

How do i use OAuth Providers with Expo React Native (Supabase v2)?

is ssupabase high latency for anyone else rn?

You should state where your instance is and you are where accessing it from as could be radically different.

i red you can host supabase locally also the db? but not find this back in the docs

can i only use supabase with a cloud database or can i host the db myself also?

ah nevermind i had to click a little deeper i guess this one https://supabase.com/docs/guides/hosting/docker

Hey everyone I need help with supabase realtime. I'm getting thousands of errors like this a second. I can't find anything ni the docs.

You also posted this in help.  Please don't double post.  Otherwise this thread is just a duplicate of the help thread.