cli
pg_handlebars
Our great sponsors
cli | pg_handlebars | |
---|---|---|
15 | 1 | |
810 | 4 | |
9.8% | - | |
9.8 | 3.5 | |
1 day ago | 3 months ago | |
Go | C | |
MIT License | MIT License |
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
-
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.
Thank you for the helpful feedback.
> Using supabase migration up would mean moving the latest migration out of the migrations folder, running supabase db reset, moving the file back in and then calling supabase migration up.
We can definitely do a better job here. I'm adding support for db reset --version flag [0]. This should allow you run migration up without moving files around directories.
> I wasn't really sure what the actual outcome would look like If I have something like this in a migration script
Agree that we can do a better job with the documentation for squash command. I will add more examples.
The current implementation does a schema only dump from the local database, created by running local migration files. Any insert statements will be excluded from the dump. I believe this is not the correct behaviour so I've filed a bug [1] to fix in the next stable release.
> We do have plans to improve the current database trigger behavior. Will share more updates on this in the coming months.
Excited to hear more! Being able to trigger functions from DB & cron triggers without having to hardcode a secret (which causes them to end up in migrations files) will be a huge improvement.
> Can you explain what do you mean by template URLs?
Oh, I had no idea that the functions routes were "wild card"! I don't think that's mentioned anywhere in the documentation, btw.
> Source maps, is it broken during local dev or when you deploy the function?
Sorry, I actually mean "import-maps": https://github.com/supabase/cli/issues/1338
"Source maps" (does deno actually use source maps?) ARE broken as well. EG: The line numbers in runtime don't line up with the function code in the IDE or even that is in the docker volume.
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
-
SPARTAN. Type-safe Angular full-stack development powered by Analog.
For more info see this issue on GitHub.
-
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
-
Can't link fresh project - problem with underlying postgrest version not supporting 15.
The errors you cite come from the https://github.com/supabase/cli not from postgREST(it does support v15).
-
Generating typescript interfaces for postgres composite types and enums?
Maybe add your voice to https://github.com/supabase/cli/issues/531
pg_handlebars
-
Generating typescript interfaces for postgres composite types and enums?
Completely agree. I think it would be better to have an extension for generating types, may be a templating based extension similar to https://github.com/RekGRpth/pg_handlebars so that types could be generated close to the source of the types, and done language independently.
What are some alternatives?
objectbox-dart - Flutter database for super-fast Dart object persistence
ng-signal-forms
supabase-on-aws - Self-hosted Supabase on AWS
Appwrite - Build like a team of hundreds_
oak - A middleware framework for handling HTTP with Deno, Node, Bun and Cloudflare Workers 🐿️ 🦕
sql-examples - Curated list of SQL to help you find useful script easily 🚀
docker - Docker - the open-source application container engine
auth - A JWT based API for managing users and issuing JWT tokens
basejump - Teams, personal accounts, permissions and billing for your Supabase app
vercel-ai-chatbot - A full-featured, Supabaseified Next.js AI chatbot built by Vercel Labs & Supabase
nx - Smart Monorepos · Fast CI
zod - TypeScript-first schema validation with static type inference