Is there something about Deno that makes Edge functions good to be based on it - Netlify also has its Edge functions in Deno https://docs.netlify.com/edge-functions/overview/ maybe just coincidence, but seen two edge functions in Deno implementations in the last hour so makes me wonder.
Supabase Edge Runtime: Self-Hosted Deno Functions
41–50 of 105 posts
Re: Supabase Edge Runtime: Self-Hosted Deno Functions
#42Request pre-processing using JavaScript is amazing! Will I be able to deploy an Astro app on supabase edge functions? I'm building a multi-tenant B2B2C product on supabase that's deployed on a customer's sub-domain, so writing reverse proxy logic in js would be a boon.
Re: Supabase Edge Runtime: Self-Hosted Deno Functions
#43Earlier quoted context omitted.
It's as bad as Deno Deploy has always been (used by Netlify edge functions, Supabase, and others). To me CF Workers are more about interacting with the CF CDN, doing lightweight HTTP stuff, etc. I would never use Workers to build a full server application. Their custom runtime locks you in, it's extremely barebones, and obviously almost no NPM modules are compatible. They are working on Node compat which will probabl…
Very well said. What would you say CF has been investing in instead?
Re: Supabase Edge Runtime: Self-Hosted Deno Functions
#44hey hn, supabase ceo here This is a webserver for Deno. It is MIT licensed, written in Rust, and based on the latest Deno Runtime (1.32+). It can serve TypeScript, JavaScript, and WASM functions. This one is important for local development and self-hosting. For local development, it ensures there is parity between development and production. For self-hosting, it means you can deploy and manage your Deno Functions on…
Any details about the removing of Kong? What did you use it for and how will this help with removing it?
The other motivation for doing this is that it makes our API Gateway programmable with user defined functions. For example, you could implement custom transformations for storage or augment the Authorization header with custom claims before calling Postgrest.
Re: Supabase Edge Runtime: Self-Hosted Deno Functions
#45Re: Supabase Edge Runtime: Self-Hosted Deno Functions
#46Earlier quoted context omitted.
I’ve been using Cloudflare workers for a while now and I have to disagree. There are entire classes of problems I no longer worry about with Workers and can just focus on building. My search history is a reflection of that. I’m no longer looking up “how do I put this thing in a Jails or container to limit exposure?” “how do I properly secure an SSH server?” “what is the magic incantation in my NGinx configuration to…
I updated my post. I meant with "deploy as VPS" "deploy as a (virtual private) server with a service like render, heroku". I agree the sys admin stuff, no thanks. the appeal of "serverless edge", at least to me, is ease of deployment. but, that ease of deployment is tooling / git integration rather than the underlying architecture. the benefit of "your functions are globally distributed" has yet to appeal to me. for…
I honestly think with containers there is much less need for stuff like render and heroku, even more so if you use SQLite and remove the hosted database complexity.
In fact in many ways it's even better - for instance the ability to run locally with an exact bit-for-bit production environment. Can't really do that with a PaaS.
Re: Supabase Edge Runtime: Self-Hosted Deno Functions
#47Earlier quoted context omitted.
Is Supabase targeted towards webdev "apps" or mobile "apps"? As a mobile dev I got excited to check out a Firebase + serverless alternative, but the docs seem very targeted towards webdevs and non-native apps. I see there's a 1.0 Swift library that's available, would love if someone can chime in with their experience using that in an iOS app.
They seem to have Flutter support but the lack of React Native support is non starter for me.
We also support swift: https://supabase.com/docs/reference/swift/introduction
One more thing - we will have some more announcements for mobile (specifically auth) tomorrow.
Re: Supabase Edge Runtime: Self-Hosted Deno Functions
#48just use a regular server for mid/larger sized apps. i started my web dev journey with JAMStack, Vercel, the "edge". everything is easy as long as one only deploys a full-stack NextJS app. the moment other apps come in, just use a server deployed as VPS and avoid "edge runtime hell". edge runtime hell refers to "you can't do this (function with over 2MB payload), you can't do that (because not supported by X)". EDIT:…
I'm coming around to building everything for a VPS from the outset. There's a lot of upside to VPSes, such as: 1. Can be purchased as a fixed cost, usually at a rate that's much cheaper than on-demand pricing, and especially serverless--this tends to only get better with time as competition keeps prices low 2. It's "just" a Unix/Windows/Mac box, so the issues with runtime constraints you mention are bounded different…
It's a journey I've been going on too.
All the new platforms and paradigms that have emerged have had an initial shallow aura of helpfulness that has drawn me in, but almost exclusively when digging in I've realised that they create more issues than they solve, and/or introduce limitations that aren't worth it and force me to write janky, overly complicated code to work around that isn't comprehensible even a few weeks hence.
Maybe the most notable exception to this is containers. But in a sense they're an abstraction over the very same VPS paradigm. So that makes sense. It's not something new or different, just the same thing but with some advantages (and disadvantages too, obviously).
Re: Supabase Edge Runtime: Self-Hosted Deno Functions
#49Do you have feature parity with Firebase. The main thing I love is getting auth up and running. The Flutter integration is also top notch.
We're also gonna be launching something auth-related this week too so stay tuned!
Re: Supabase Edge Runtime: Self-Hosted Deno Functions
#50Earlier quoted context omitted.
They seem to have Flutter support but the lack of React Native support is non starter for me.
Actually React Native is supported with the JS libs. While we don't have React Native docs, here is one for Expo which should be easy enough to convert: https://supabase.com/docs/guides/getting-started/tutorials/w... We also support swift: https://supabase.com/docs/reference/swift/introduction One more thing - we will have some more announcements for mobile (specifically auth) tomorrow.