cli
storage
cli | storage | |
---|---|---|
16 | 19 | |
869 | 654 | |
6.8% | 10.2% | |
9.8 | 8.4 | |
4 days ago | 5 days ago | |
Go | TypeScript | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cli
-
How To Make An Insanely Fast AI App (Supabase, LLAMA 3 and Groq)
You'll need to install the Supabase CLI in different ways depending on your OS, check out this guide for details and come right back here.
-
We really need a way to know the remote stack container/image versions and be able to set them on local config.
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.
-
Deno.land is down, which means Supabase functions are down locally
@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
-
Supabase Local Dev: migrations, branching, and observability
> 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.
-
Any comprehensive guide on self hosting ?
I think we've been working on that recently here: https://github.com/supabase/cli/pull/907
-
Using current_setting('request.cookies', true) to read request cookies doesn't seem to work
Can you try it locally with the supabase CLI? https://github.com/supabase/cli
-
SPARTAN. Type-safe Angular full-stack development powered by Analog.
For more info see this issue on GitHub.
-
Opaque errors trying to serve and deploy edge functions
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.
-
The Case for better Self-Hosted Supabase Support
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
storage
-
Supabase Storage: now supports the S3 protocol
[3] https://github.com/supabase/storage/issues/439
The Supabase Storage Engine is fully open source and is one of the few storage solutions that offer 3 interoperable protocols to manage your files:
-
What's the simplest solution to sell digital downloads via SvelteKit?
For instance, consider a supabase setup where you place your photos in storage and your orders in a table. Then, have a function run automatically whenever a new row is added to the orders table. That function would be responsible for identifying what the customer bought and delivering it to them.
-
Managify: Manage Your Teams Easily
In this page, I used Supabase Storage to store the files uploaded by the users
-
HELP -> ERROR: function st_point(double precision, double precision) does not exist (SQLSTATE 42883)
-- Create a table for public profiles CREATE TABLE profiles ( id UUID REFERENCES auth.users ON DELETE CASCADE PRIMARY KEY, updated_at TIMESTAMP WITH TIME ZONE, username TEXT NULL, full_name TEXT, profile_image_url TEXT, bio TEXT, sex SMALLINT DEFAULT 0, CONSTRAINT username_length CHECK (CHAR_LENGTH(username) >= 3) ); -- Create a table for channeles CREATE TABLE channeles ( id SERIAL PRIMARY KEY, userRefId UUID REFERENCES auth.users(id), channel TEXT, updated_at TIMESTAMP WITH TIME ZONE ); -- Create a table for geo location CREATE TABLE user_geo ( id SERIAL PRIMARY KEY, userRefId UUID REFERENCES auth.users(id), location GEOGRAPHY(point) NOT NULL, updated_at TIMESTAMP WITH TIME ZONE ); create index user_geo_index on public.user_geo using GIST (location); -- Set up Row Level Security (RLS) -- See https://supabase.com/docs/guides/auth/row-level-security for more details. ALTER TABLE profiles ENABLE ROW LEVEL SECURITY; CREATE POLICY "Public profiles are viewable by everyone." ON profiles FOR SELECT USING (TRUE); CREATE POLICY "Users can insert their own profile." ON profiles FOR INSERT WITH CHECK (auth.uid() = id); CREATE POLICY "Users can update own profile." ON profiles FOR UPDATE USING (auth.uid() = id); -- Set up Row Level Security (RLS) -- See https://supabase.com/docs/guides/auth/row-level-security for more details. ALTER TABLE channeles ENABLE ROW LEVEL SECURITY; CREATE POLICY "Public channeles are viewable by everyone." ON channeles FOR SELECT USING (TRUE); CREATE POLICY "Users can insert their own channeles." ON channeles FOR INSERT WITH CHECK (auth.uid() = userRefId); CREATE POLICY "Users can update own channeles." ON channeles FOR UPDATE USING (auth.uid() = userRefId); -- Set up Row Level Security (RLS) -- See https://supabase.com/docs/guides/auth/row-level-security for more details. ALTER TABLE user_geo ENABLE ROW LEVEL SECURITY; CREATE POLICY "Public geo_location are viewable by everyone." ON user_geo FOR SELECT USING (TRUE); CREATE POLICY "Users can insert their own geo_location." ON user_geo FOR INSERT WITH CHECK (auth.uid() = userRefId); CREATE POLICY "Users can update own geo_location." ON user_geo FOR UPDATE USING (auth.uid() = userRefId); -- See https://supabase.com/docs/guides/auth/managing-user-data#using-triggers for more details. CREATE OR REPLACE FUNCTION public.handle_new_user() RETURNS TRIGGER AS $$ BEGIN INSERT INTO public.profiles ( id, updated_at, username, full_name, profile_image_url, bio, sex, ) VALUES ( NEW.id, NOW(), NEW.raw_user_meta_data->>'username', NEW.raw_user_meta_data->>'full_name', NEW.raw_user_meta_data->>'profile_image_url', NEW.raw_user_meta_data->>'bio', COALESCE(CAST(NEW.raw_user_meta_data->>'sex' AS SMALLINT), 0), ); INSERT INTO public.channeles (userRefId, channel, updated_at) VALUES (NEW.id, NEW.raw_user_meta_data->>'expoToken', NOW()); INSERT INTO public.user_geo (userRefId, location, updated_at) VALUES ( NEW.id, ST_Point(CAST(NEW.raw_user_meta_data->>'lat' AS FLOAT), CAST(NEW.raw_user_meta_data->>'lng' AS FLOAT)), NOW() ); RETURN NEW; END; $$ LANGUAGE plpgsql SECURITY DEFINER; CREATE TRIGGER on_auth_user_created AFTER INSERT ON auth.users FOR EACH ROW EXECUTE FUNCTION public.handle_new_user(); -- Set up Storage! INSERT INTO storage.buckets (id, name) VALUES ('profile_images', 'profile_images'); -- Set up access controls for storage. -- See https://supabase.com/docs/guides/storage#policy-examples for more details. CREATE POLICY "profile_image images are publicly accessible." ON storage.objects FOR SELECT USING (bucket_id = 'profile_images'); CREATE POLICY "Anyone can upload a profile_image." ON storage.objects FOR INSERT WITH CHECK (bucket_id = 'profile_images');
-
Supabase alternatives
For example the storage-api. I was on version supabase/storage-api:v0.29.1 for a long time, until I realized, that there is a new version of it (0.40.1). Fast forward, upgraded everything, checked my application and everything storage related stopped working. From now on it's always the same procedure. Debugging the errors, digging through the code on GitHub, checking commits, issues, etc. After a while I found a bug from 2019 which had exactly the same error as I, tested the workaround and it worked again (partially, workaround).
-
A Rounded Solution to Image Handling on the OpenSauced Dashboard
Alternatively, we could use imagemagick (cli tool for image transforms) + supabase storage to do the same for free.
-
AWS Amplify Is a Grift
[5] https://supabase.com/docs/guides/storage
-
Building a Startup from Scratch: My Mistakes as CTO
Storage
-
Any idea how to limit file upload size ?
We'll probably need to upload other types of assets in the future, so having a way to set the limit per bucket would be nice... There's an issue for this - I may make a PR to implement it at some point.
What are some alternatives?
objectbox-dart - Flutter database for super-fast Dart object persistence
supabase - The open source Firebase alternative.
ng-signal-forms
supabase-js - An isomorphic Javascript client for Supabase. Query your Supabase database, subscribe to realtime events, upload and download files, browse typescript examples, invoke postgres functions via rpc, invoke supabase edge functions, query pgvector.
supabase-on-aws - Self-hosted Supabase on AWS
auth - A JWT based API for managing users and issuing JWT tokens
oak - A middleware framework for handling HTTP with Deno, Node, Bun and Cloudflare Workers 🐿️ 🦕
nextjs-auth0 - Next.js SDK for signing in with Auth0
Appwrite - Your backend, minus the hassle.
postgrest - REST API for any Postgres database
sql-examples - Curated list of SQL to help you find useful script easily 🚀
fastify-multipart - Multipart support for Fastify