Settings > API > Extra search path

Does that not set paths for every session though? That might be OK for extensions, but in a security definer function you are encouraged to set the path directly so user can't change the session path. Also if you need access to a private schema or auth you would not want that in the extra search path in the API. I guess you could also just prepend your schemas in the function call though as needed if not in the general path.

Cron Jobs

WebAuthn support would be great

While the launch week process may generate more publicity/excitement, as Supabase matures and you have a large base of production products running on your servers, I recommend you either phase in actual implementation of your launched stuff, or back off a bit. Seems like your small workforce is stretched getting the launch stuff out, and then are tasked with having to deal with fires as a lot of users hit your new stuff and find either real bugs, or just new stuff. You caution alot of stuff is Beta/Alpha, but at same time seems many of your users are running with real users on their products. Luckily I'm not yet, as realtime would have my entire user base down today, for something I did not even plan on worrying about as I did not think upgrade to RLS would hit me until I decided to start using/testing it. FWIW.

Thanks for the candid feedback @User . We will certainly be doing a post-mortem on all the issues and a retrospective after Launch Week. Also - I appreciate all your comments here & on GitHub - they've been helpful for use while we worked through the issues

Bucket related Suggestions: - Being able to CNAME a Domain to a Bucket i.e. naming a bucket

supabase.media

and setting a CNAME on that domain to

${project}.supabase.co

- Renaming Buckets from the Dashboard - [Self-Hosted] Being able to set

SUPABASE_S3_URL

,

SUPABASE_S3_SECRET

,

SUPABASE_S3_KEY

and have Supabase use that instead of the local fs

Hello Team, I was wondering if Supabase will support multi-language Auth templates anytime soon? I really love the esthetic of Supabase and would like to use it in production soon ;)

Supabase repo consists of studio, website, and docs code. Why don't we just create 3 separate repositories? and maybe add those 3 repository's submodules in the main supabase repo? So, that it would look clean and will be easy to maintain tho.

Repo split

Hello guys, I wanted to know if version branching like planet scale is something that could come up in a future on Supabase ?

Hello guys, i would like to suggest to allow other login method to supabase dashboard, i work with non tech people and i would love to let the access to db to edit some data, but they need a github account

Login Providers for Dashboard

Hi there, I wonder if Supabase have schema api which developers can create table or add columns through code

I use Airtable heavily, main reason is i can create form and get user input easily. I love supabase and want to create such feature. In this way, I don't need to sync data from airtable to supabase..

To create this feature, I think we need the schema api..

let’s open source the @SupaBot if it’s not open sourced yet.

Who is SupaBot?

Access APIs (ex. Google) through Supabase

Maybe create a new channel for reporting issues. I know that, in general, bugs should be reported in GitHub and unexpected downtime or blockers can be reported via the dashboard, but since people also use Discord for such problems anyway, a dedicated channel might be worth it

Hey guys! Not sure if this is a proposal or an issue, or something related with a specific auth provider. Description Im working with github auth, and works fine, something simple as:

await supabase.auth.signIn({
    provider: "github",
});

Probably you already know that by doing this.. in case a user doesnt exist in supabase, its created, so this signIn works like a singUp when the user doesnt exist, and thats totally fine, I would say I like the approach, but would be possible, to get a response info from

auth.signIn

to know if the user has been created or just logged? would make sense? I know I could check if the user exist before or something else, but I think is something very useful. Maybe its already doing something similar and I was not able to figure out how to get that from the response.

detect if user is new for social provider sign up

Has anyone ever used both supabase and firebase on a project? I have one where I think it could benefit but wanted to make sure I wasn't insane

bug reporting

supabase api

I guess the numbers should be updated at https://supabase.com/docs/oss, or even the list of repos

Coming from Firebase, there are two things that I find I miss a lot: (1) optimistic updates, and (2) connection self-healing (e.g., when a user closes their laptop and reopens it). Are these common pain points, or am I perhaps missing something? If not, I'm curious what the common workarounds are. I ended up rolling my own on my latest project, but that doesn't feel like the right solution.

(I'm talking here about realtime subscriptions in particular.)

is it possible for supabase pro to be included in the github student pack

Looks like its very out of date as its static data