we still have a lot of cleanup before I'd use this as a model, but the rough strategy we employed is:
1. Hide sensitive code behind an API
2. Open source everything else (regardless of Platform/Self-Hosted
3. Use env vars and feature flags to determine what is visually displayed
The docker-compose for self-hosted is the same stack as every project on the Platform which helps.
You, Ant and the others are killing it. Looking forward to the security updates coming to Realtime. I know that was a blocker for myself and a few others.
thanks for the kind words. We just released realtime updates (about 20 mins ago) - we have a few launches this week and that's the one I'm most excited about
tbd on the timeline here - we know that there are already platforms (like Vercel, Netlify, Deno, CF Workers) doing amazing work here, so we're spending more effort on the under-served problems.
Would love to know your use-case, or why you'd prefer Supabase as a Function provider over one of the existing players? It's helpful for us to design the system around any weaknesses/difficulties you're facing
For me, the BaaS philosophy is to simplify development by using an "all-batteries-included" platform. I know some people use Supabase just for the free postgres or other things, but I don't like to use multiple providers for a single simple project. That's why it makes no sense to me currently to use Supabase until there is no functions.
Comments
We did a write-up on the tech stack and some of the approaches we considered for sharing code between our Platform and the Self-Hosted versions here: https://supabase.com/blog/2021/11/30/supabase-studio
We aim to get these to parity with each other, excepting some billing/server management features.
A big shout out to Sentry who do served as a good model for us (https://develop.sentry.dev/sentry-vs-getsentry/)
Any more details you are willing to share on how the shared code is imported and extended on the platform side?
We have a similar split, and currently use lerna to publish a collection of individual packages that get imported and extended on the other side.
we still have a lot of cleanup before I'd use this as a model, but the rough strategy we employed is:
The docker-compose for self-hosted is the same stack as every project on the Platform which helps.You, Ant and the others are killing it. Looking forward to the security updates coming to Realtime. I know that was a blocker for myself and a few others.
thanks for the kind words. We just released realtime updates (about 20 mins ago) - we have a few launches this week and that's the one I'm most excited about
Link: https://supabase.com/blog/2021/12/01/realtime-row-level-secu...
How long until we get functions running? Absolutely love the product btw, can't make the switch until we have functions tho :)
tbd on the timeline here - we know that there are already platforms (like Vercel, Netlify, Deno, CF Workers) doing amazing work here, so we're spending more effort on the under-served problems.
Would love to know your use-case, or why you'd prefer Supabase as a Function provider over one of the existing players? It's helpful for us to design the system around any weaknesses/difficulties you're facing
For me, the BaaS philosophy is to simplify development by using an "all-batteries-included" platform. I know some people use Supabase just for the free postgres or other things, but I don't like to use multiple providers for a single simple project. That's why it makes no sense to me currently to use Supabase until there is no functions.
makes sense, and seems to be the most common reason when we ask (along with using other/preferred languages). thanks for taking the time to share