- Not to worry, our specialist engineers are here to help. Submit a support ticket through the{' '} - Dashboard. -
++ Not to worry, our specialist engineers are here to help. Submit a support ticket through + the Dashboard. +
+
*/}
-
- 
+ {tag.description}
+{tag.description}
+{tag.description}
++ +Specialized engines are always going to outperform general-purpose ones. The question is whether +the specialized engine is going to have such a significant difference in performance that it can +overcome the limitations of a general purpose one. + +... + +The challenge oftentimes is this: is the benefit you're getting from a specialized engine +because the _Engine_ is different or the _API_ is different?. + ++ +He goes on to explore the benefits of a Graph database vs a Relational database. + +Our recent release of [pg_graphql](https://github.com/supabase/pg_graphql/) closes the gap on the graph use-case by building a GraphQL API directly into Postgres as an extension. While a specialized graph database might provide performance benefits over Postgres, perhaps one of the largest benefits is simply the Graph API which makes it easier to reason about the data. + +With the introduction of Wrappers, we're hoping to close the gap on even more of these type of workloads. + +An exciting part of the FDW approach is that it provides a common interface to the world: SQL. While it has many shortcomings, SQL is the lingua franca of data. Postgres' FDWs transform any API into a data set with a common interface. This “interface aggregator” is similar to the [promise](https://medium.com/vicetech/graphql-the-great-aggregator-bcf52fe390d9) of GraphQL engines. The benefit of embedding this functionality in the database is that it exists at the _lowest level of the tech stack_. Everything that is built on top can leverage it. While Postgres cannot easily access the functionality of a GraphQL server, a GraphQL server can easily access the functionality of Postgres. + +The FDW interface also future-proofs Postgres. Instead of keeping up with the latest technological advances, Postgres can instead act as an interface whenever they develop. The recent advance in AI and ML is a great example of this: AI technology is developing faster than the time it would take to build a new “AI database”. With a FDW, Postgres can become the interface to this technology and many other technological advances in the future. + +## Developing Wrappers + +Postgres has a builtin “Postgres FDW” allows querying one Postgres database from another. We've extended this functionality to support a variety of data sources, from Data Warehouses to APIs. +This release includes two initial wrappers: Stripe and Firebase + +| Integration | Platform | Self-hosted | select | insert | update | delete | +| ----------- | -------- | ----------- | -------------------------------------------------- | -------------------------------------------------- | -------------------------------------------------- | -------------------------------------------------- | +| Firebase | 🚧 | ✅ | ✅ | 🚧 | 🚧 | 🚧 | +| Postgres | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| Stripe | 🚧 | ✅ | ✅ | 🚧 | 🚧 | 🚧 | + +With several more [under development](https://github.com/supabase/wrappers/tree/main/wrappers/src/fdw): + +| Integration | select | insert | update | delete | +| ----------- | -------------------------------------------------- | -------------------------------------------------- | -------------------------------------------------- | -------------------------------------------------- | +| Airtable | ✅ | 🚧 | 🚧 | 🚧 | +| BigQuery | ✅ | ✅ | ✅ | ✅ | +| ClickHouse | ✅ | ✅ | ✅ | ✅ | + +Wrappers used [pgx](https://github.com/tcdi/pgx), extending it with FDW support. pgx is a Postgres extension framework written in Rust. Wrappers is very similar to [Steampipe](https://steampipe.io/) or [Multicorn](https://multicorn.org/). We opted to develop our own framework for several reasons: + +- The current state of FDWs is in disarray. It's hard to know which FDWs are supported and functional. We think there's a benefit to colocating all FDWs in a single repository using modern tooling. This makes contributing simpler and maintenance faster. +- Wrappers has async support, which enables the development of RESTful API-based FDWs, like Stripe. +- It's written in Rust, which provides reliable performance, strong typing, data security, and “push down” is supported through the framework. + +## Supported types and Push Down + +Wrappers [supports](https://github.com/supabase/wrappers/blob/83887dcc2ddcf972ca1b1eec4a598cd7bff947de/supabase-wrappers/src/interface.rs#L11) a variety of types, including: +`bool`, `i8`, `i16`, `f32`, `i32`, `f64`, `i64`, `String`, `Date`, `Timestamp`, and `JsonB`. + +Foreign Data Wrappers have a concept of "push down". This means that the FDW runs the query on _remote_ data source. This is useful for performance reasons, as the remote data source can often perform the query more efficiently than Postgres. Push down is also useful for security reasons, as the remote data source can enforce access control. Limited push-down support has been added as a Proof of Concept, but this will be a key focus of Wrappers. + +You can follow development of all the Wrappers in the official [GitHub Repo](https://github.com/supabase/wrappers). + +## Next Steps + +We're not "officially" releasing Wrappers onto the platform yet, although the brave and curious might be able to figure out how to use it "unofficially". Caveat emptor: there will be breaking changes. + +We're excited to see what the community does with Wrappers. We're hoping that Wrappers will help to accelerate the adoption of Postgres as a data hub. +If you're interested in getting involved or building your own Wrapper, don't hesitate to jump into the code and start developing with us. + +- Star & Watch the GitHub repo: [github.com/supabase/wrappers](https://github.com/supabase/wrappers) +- View the documentation: [supabase.github.io/wrappers](https://supabase.github.io/wrappers/) +- Supabase Launch Week: [supabase.com/launch-week](https://supabase.com/launch-week) + + + +## More Launch Week 6 + +- [Day 1: New Supabase Docs, built with Next.js](https://supabase.com/blog/new-supabase-docs-built-with-nextjs) +- [Day 2: Supabase Storage v2: Image resizing and Smart CDN](https://supabase.com/blog/storage-image-resizing-smart-cdn) +- [Day 3: Multi-factor Authentication via Row Level Security Enforcement](https://supabase.com/blog/mfa-auth-via-rls) +- [Launch Week 6 Hackathon](https://supabase.com/blog/launch-week-6-hackathon) +- [Who We Hire at Supabase](https://supabase.com/blog/who-we-hire) +- [pg_crdt - an experimental CRDT extension for Postgres](https://supabase.com/blog/postgres-crdt) diff --git a/apps/www/_blog/2022-12-16-custom-domain-names.mdx b/apps/www/_blog/2022-12-16-custom-domain-names.mdx new file mode 100644 index 00000000000..014255f71a8 --- /dev/null +++ b/apps/www/_blog/2022-12-16-custom-domain-names.mdx @@ -0,0 +1,67 @@ +--- +title: Custom Domain Names +description: Change your Supabase project's domain name to your own domain. +author: div_arora +image: launch-week-6/custom-domains/og-custom-domains.png +thumb: launch-week-6/custom-domains/og-custom-domains.png +tags: + - launch-week +date: '2022-12-16' +toc_depth: 3 +--- + +After your side-project becomes wildly viral, and you've graduated into a “serious business”, delivering a more branded experience is probably one of the items at the bottom of your checklist. + +To that end, we're releasing custom domains, and vanity subdomains, to help you present a more polished product to your users. + +# Custom Domains + +Custom domains allow you to use your own domain for your Supabase project. + +Instead of seeing: + +`sqvfdnkeiuztnsinmtau.supabase.co` + +your users instead interact with + +`api.example.com`: + + + +Today, we're making Custom Domains generally available, and they're now accessible as a paid add-on through the Supabase dashboard. + +Get your custom domain in the [Dashboard](https://app.supabase.com/project/_/settings/general) + +# Vanity Subdomains + +Vanity Subdomains allow you to choose a subdomain on Supabase's own domain. + +Instead of hosting your services on a randomly assigned subdomain: + +`abcdefghijklmno.supabase.co` + +you can choose one that's relevant to your project, for example: + +`my-example-brand.supabase.co` + +Vanity Subdomains are offered at no additional cost for all projects on a paid plan, and are being launched in a closed beta. + +Instructions for setting up Vanity Subdomains are now available in our [docs](https://supabase.com/docs/guides/platform/custom-domains#vanity-subdomains). + +## Limitations + +In this release, we still have some limitations that we're working through: + +1. Edge Functions don't support custom domains or vanity subdomains yet, so you have to use the current endpoint to access them. +2. Right now, you can only set up one custom domain or vanity subdomain per project. + +We're working hard to fix these limitations, so stay tuned for future updates. + +## More Launch Week 6 + +- [Day 1: New Supabase Docs, built with Next.js](https://supabase.com/blog/new-supabase-docs-built-with-nextjs) +- [Day 2: Supabase Storage v2: Image resizing and Smart CDN](https://supabase.com/blog/storage-image-resizing-smart-cdn) +- [Day 3: Multi-factor Authentication via Row Level Security Enforcement](https://supabase.com/blog/mfa-auth-via-rls) +- [Launch Week 6 Hackathon](https://supabase.com/blog/launch-week-6-hackathon) +- [Who We Hire at Supabase](https://supabase.com/blog/who-we-hire) +- [pg_crdt - an experimental CRDT extension for Postgres](https://supabase.com/blog/postgres-crdt) diff --git a/apps/www/_blog/2022-12-16-launch-week-6-community-day.mdx b/apps/www/_blog/2022-12-16-launch-week-6-community-day.mdx new file mode 100644 index 00000000000..b0c7f395dc8 --- /dev/null +++ b/apps/www/_blog/2022-12-16-launch-week-6-community-day.mdx @@ -0,0 +1,240 @@ +--- +title: 'Community Day' +description: Wrapping up Launch Week 6 with contributors, partners, and friends. +author: andrew_smith,jonmeyers_io,thor_schaeff,tyler_shukert +image: lw6-community/community-day.png +thumb: lw6-community/community-day.png +tags: + - launch-week + - community +date: '2022-12-16' +toc_depth: 3 +--- + +Supabase is a collaborative company. We work with, sponsor, and support as many open source tools as possible. The great thing about this approach is that each tool brings their own community and it's starting to feel like Supabase is really just a “community of communities”. Far too much has happened in the Supabase community in the last 3 months for us to possibly feature it all here, so here's a collection of the highlights! + +## New Integrations + +While we've been working hard on new features, the community has been developing a healthy [integrations marketplace](https://supabase.com/docs/guides/integrations/integrations). Since Supabase is just Postgres, any tool which works with Postgres works with Supabase (no additional changes required). Today we're adding a few major players to the roster: + +### FlutterFlow + + + +[FlutterFlow](https://flutterflow.io/) is a low-code builder for developing native mobile applications using Flutter. You can use the simple drag-and-drop interface to build your app faster than traditional development. + +An integration between FlutterFlow and Supabase has been long awaited by the community. Starting today, you can build your apps with FlutterFlow and use Supabase for your backend! + +This is just the beginning of our integration with FlutterFlow. We're working closely with the FlutterFlow team to deliver more features! + +Watch John from the FlutterFlow team demonstrate how you can [get started with FlutterFlow and Supabase](https://youtu.be/hw9Q-NjASbU). + +### OneSignal + + + +[OneSignal](https://onesignal.com/) is a messaging platform allowing you to deliver push notifications, in-app messages, SMS, and emails to your users. + +Combining OneSignal with Supabase, you can send cloud messages to your users with any database change. + +We have guides on how to get started with [Next.js and OneSignal](https://supabase.com/docs/guides/integrations/onesignal), and [Flutter and OneSignal](https://github.com/OneSignalDevelopers/onesignal-supabase-sample-integration-supabase). + +In the video above, William from OneSignal will show you how you can easily integrate OneSignal with your Supabase app. + +### NextAuth + + + +[NextAuth.js](https://next-auth.js.org/) is an open source authentication solution for [Next.js](https://nextjs.org/). It allows you to bring your own Database so that you own your user data. + +The amazing NextAuth community who have built a [Supabase Adapter](https://next-auth.js.org/adapters/supabase) that makes it easy to use NextAuth.js with Supabase, and enables the use of [Row Level Security (RLS) policies](https://next-auth.js.org/adapters/supabase#enabling-row-level-security-rls). + +In [this community spotlight video](https://youtube.com/EdYQ9fF-hz4), [Thang Huu Vu](https://twitter.com/thanghvu), the lead maintainer of NextAuth.js, gives an overview and brief history of NextAuth, followed by a tutorial on how to set up the new Supabase Adapter. + +## Postgres Ecosystem + +### PGroonga Multilingual Search extension + + + +Over the past few years, we've had a number of people ask if we can add Full Text Search for other languages. PGroonga has been on our radar for a long time now, so when we reached out to them we were surprised to learn that _no_ Postgres platform currently supports them. Today we're fixing this by becoming the first. + +PostgreSQL of course features excellent [Full Text Search](https://supabase.com/docs/guides/database/full-text-search) out-the-box, but it can be lacking if you need to search against languages with non-Roman characters such as Japanese, Chinese and so on. For this you can use the PGroonga extension! It's already installed on all new projects, just head to the [Database tab](https://app.supabase.com/project/_/database/extensions) on the dashboard and search or scroll for 'PGroonga' and hit enable to get started. Once enabled you can head to [their excellent documentation](https://pgroonga.github.io/tutorial/) on how to start making queries. + +PGroonga is backed by a collection of incredible maintainers, contributors, and a broad and diverse [community](https://pgroonga.github.io/community/). + +### PostgreSQL 15 + + + +The PostgreSQL community [released](https://www.postgresql.org/docs/current/release-15.html) version 15 (stable) in October 2022. All Projects created on the Supabase platform from today will be on version 15. If you want to upgrade one of your existing Projects, check out our [Upgrading](https://supabase.com/docs/guides/platform/migrating-and-upgrading-projects#upgrade-your-project) documentation, and if you want to see what's new, check out : XXX + +Read [what's new in **Postgres 15?**](https://supabase.com/blog/new-in-postgres-15) + +### PostgREST version 11 pre-release + + + +PostgREST 11 is not wrapped up yet but you can try a pre-release locally with the Supabase CLI. Some of the new features include: spreading related tables, related orders and anti-joins. Read on more about these on: + +[Learn more about PostgREST 11](https://supabase.com/blog/postgrest-11-prerelease) + +## Made with Supabase + + + +Perhaps you've seen [madewithsupabase.com](https://www.madewithsupabase.com/), but did you know that the site was made and is maintained by an [open source contributor](https://twitter.com/zernonia) (during our first hackathon)? Since then, there have been over 300 apps and websites listed. Here's some of our favourites: + +### LottieFiles + +LottieFiles built a [Mobile Motion Canvas](https://www.youtube.com/watch?v=QoN7l_Wq_S4) where you can create and share social stories, posts, stickers, & more. + +### Mobbin + +Mobbin use Supabase Auth to power their [UI/UX library of Mobile and Web screenshots](https://mobbin.com/browse/ios/apps). Last year they [migrated 200k users from Firebase to Supabase Auth](https://supabase.com/blog/mobbin-supabase-200000-users). + +### sound.xyz + +[sound.xyz](https://sound.xyz) is platform for artists to drop tracks to their fans first, users support the artists they love directly and stake their claim on being there before everyone else. + +### Topaz + +[Topaz](https://topaz.network/) is one of the fastest growing NFT networks and chose supabase as a backend to ensure they won't lose customers during peak traffic periods. + +### Repeat.dev + +[Repeat.dev](https://repeat.dev) is a platform for webhook based task automation. It has a built in scheduler, and can handle emails and pdf generation. + +### Dots + +[Dots](https://www.dots.community/) is a tool for interactive onboarding and support flows across Slack and Discord. Dots uses Supabase so they don't have to worry about managing a backend, and can focus on helping their users build amazing community experiences. + +### Fleeting Notes + +[Fleeting Notes](https://www.fleetingnotes.app/) allows you to take linked notes within your browser or on your phone, then sync the notes with Obsidian. They wrote an awesome guide on how they [migrated 1000+ users from Firebase to Supabase](https://fleetingnotes.app/posts/migrating-from-firebase-to-supabase/). + +## Content Creators + + + +One of the most exciting developments this year is the number of content creators and developers helping _others_ to get started with Supabase. Ultimately, this means more developers using Postgres. There's really too many of these awesome folks to feature, but here's a few who have gone above and beyond: + +### Content Storm + +More than 30+ creators featured in our [Content Storm](https://supabase.com/blog/the-supabase-content-storm). These folks all produced brand new content in the build up to Launch Week and dropped it simultaneously! + +### Supaship + + + +Supaship built a whole [Supabase course](https://supaship.io/). It's absolutely jam-packed with advice on how to get the most out of Supabase (and his meme game is absolute fire!). + +### Jon Meyers for Egghead + + + +Check out Jon's brand new, entirely free course on egghead to learn all about the Supabase Auth Helpers. Throughout the course, you will build a realtime chat application with Remix and learn how to: + +- use Supabase server-side in loaders and actions +- query and mutate data as an authenticated user with Supabase +- sign users in with GitHub OAuth +- enforce authorization with Row Level Security (RLS) policies +- merge client and server state with realtime events +- deploy a Remix app to Vercel + +[Build a Realtime Chat App with Remix and Supabase](https://egghead.io/courses/build-a-realtime-chat-app-with-remix-and-supabase-d36e2618) + +### Everything Svelte + + + +[Everything Svelte](https://www.everythingsvelte.com/) is a Sveltekit and Supabase course by [Amy](https://twitter.com/selfteachme). You'll learn everything you need to know to build a modern web application. + +> In Everything Svelte, participants will learn EVERYTHING they need to know to build a full-stack application in SvelteKit and Supabase. We cover topics such as Tailwind styles, Svelte animations and transitions, search, testing, creating components, managing state, Stripe integration, sending emails, GitHub Actions, database modeling, and deployment. Supabase, in particular, really shines as we leverage its authentication system, row level security, local storage, and database APIs. + +## Getting started templates + +### Base Jump + +[usebasejump.com](https://usebasejump.com/) is "The fastest way to launch Supabase apps with NextJS". Basejump is open source. Contributions are both awesome and encouraged! + +### supastarter + +[supastarter.dev](https://supastarter.dev/) is the SaaS starter template for Next.js and Supabase. Save time and focus on your business with this scalable and production-ready starter template for your SaaS. It includes authentication, i18n, subscriptions, landing page and much more! + +## Community libraries + + + +The Supabase-Community org is home to 80(!) repos built and maintained by the community. It houses everything from [Client Libraries](https://github.com/supabase-community/#client-libraries), to [Auth Helpers](https://github.com/supabase-community/#supabase-auth-helpers), [Self Hosting tooling](https://github.com/supabase-community/#self-hosting), and [Utilities](https://github.com/supabase-community/#utilities). + +An awesome recent addition from the AWS team is [supabase-on-aws](https://github.com/supabase-community/supabase-on-aws), a self-hosting starter kit for AWS. + +## Community Growth + + + +At the start of this year [@kiwicopple tweeted](https://twitter.com/kiwicopple/status/1478338320346267648) how far we had come as a community. Since then we've grown to one of the [most popular](https://github.com/search?q=stars%3A%3E42000&type=repositories) repos on GitHub (top 220) and have grown by: + +- GitHub stars: 25K → 60K (across all repos) +- Hosted Databases: 75K → 250K +- Contributors: 271 → 750 (across all repos) +- Launch Weeks: 3 → 6 +- Discord: 0 → 11k + +## Giving back + +At less than 3 years old we're still finding our feet, but one of the things we're most proud of is our contribution back to open source. Technically everyone working at Supabase is an open source contributor, so it's hard to quantify exactly the value we've been contributing to the open source ecosystem. To name a few of the more obvious ways: + +- Paid out over $100,000 to contributors via [Open Collective](https://opencollective.com/supabase). +- Invested in $500,000 into [OrioleDB](https://github.com/orioledb/orioledb) to accelerate the Table Access API in Postgres. +- We financially sponsor open source tools, like [PostgREST](https://opencollective.com/supabase-postgrest) and [PGroonga](https://opencollective.com/clear-code), and research initiatives like [Elixir type system](https://twitter.com/josevalim/status/1535008937640181760?s=20&t=BLqeO2YpdhYfCZxgsmlNug). +- We employ maintainers of the external tools which we use, including PostgREST and pgsodium (to work on those tools)! +- Our team has contributed several patches to the Postgres core. +- We help to drive open source adoption on tools like [Deno](https://deno.land/). +- We collaborated with the [Snaplet](https://www.snaplet.dev/) team to develop and open source [Postgres WASM](https://supabase.com/blog/postgres-wasm). +- And possibly the biggest: we've maintained our OSI-compliant stance. With the exception of some of our cloud-infra & billing code, the Supabase ecosystem is all MIT, Apache 2.0, or PostgreSQL licensed. + +We plan to continue our open and collaborative trend. There are many companies working on exciting ideas in the database ecosystem, and there are far too many problems for the Supabase team to solve alone. If you're interested in working with us to solve these problems, don't ever hesitate to reach out. + +## Getting involved + +- Want to contribute? Dive into any of our [repos](https://github.com/supabase/) to get started. +- Want to work in open source? We don't have many openings today, but keep this URL in mind in the future when you're job-hunting: [supabase.com/careers](https://supabase.com/careers) +- Want to try out Supabase? [Join the Hackathon](https://supabase.com/blog/launch-week-6-hackathon) and win some nice prizes. +- Want to support us? Just a [GitHub star](https://github.com/supabase/supabase) is enough ⭐. + +## More Launch Week 6 + +- [Day 1: New Supabase Docs, built with Next.js](https://supabase.com/blog/new-supabase-docs-built-with-nextjs) +- [Day 2: Supabase Storage v2: Image resizing and Smart CDN](https://supabase.com/blog/storage-image-resizing-smart-cdn) +- [Day 3: Multi-factor Authentication via Row Level Security Enforcement](https://supabase.com/blog/mfa-auth-via-rls) +- [Day 4: Supabase Wrappers, a Postgres FDW framework written in Rust](https://supabase.com/blog/postgres-foreign-data-wrappers-rust) +- [Who We Hire at Supabase](https://supabase.com/blog/who-we-hire) diff --git a/apps/www/_blog/2022-12-16-launch-week-6-wrap-up.mdx b/apps/www/_blog/2022-12-16-launch-week-6-wrap-up.mdx new file mode 100644 index 00000000000..f8435ebed42 --- /dev/null +++ b/apps/www/_blog/2022-12-16-launch-week-6-wrap-up.mdx @@ -0,0 +1,207 @@ +--- +title: 'Launch Week 6: Wrap Up' +description: "That's a wrap on Supabase Launch Week Day 6. Here's everything we shipped in one long blog post." +author: paul_copplestone +image: launch-week-6/wrap-up/og-wrap-up.png +thumb: launch-week-6/wrap-up/og-wrap-up.png +tags: + - launch-week +date: '2022-12-16' +toc_depth: 3 +--- + +That's a wrap on Supabase Launch Week Day 6. Here's everything we shipped in one long blog post. + +## New Docs, built with Next.js + + + +
+ {docs && (
+
+
+ 
+ 
+ 
+
- As a database company, being SOC2 compliant is important when handling sensitive - customer data. Supabase is currently SOC2 Type 1 compliant and we're also working on - getting certified for SOC2 Type 2 and HIPAA next. -
- -You can request for our latest SOC 2 document by submitting your request here.
- -+ Choose the database instance size that best fits your needs +
- Choose the database instance size that best fits your needs -
+ + + }> + About compute add-ons + + +- Your new subscription will begin immediately after payment -
- - ) : ( - <> -+
+ Your new subscription will begin immediately after payment +
+ + ) : ( + <> +Your billing cycle will reset after payment
*/} - - )} -Enable spend cap
-- If enabled, additional resources will not be charged on a per-usage basis -
-Enable spend cap
++ If enabled, additional resources will not be charged on a per-usage basis +
+Make owner
-Transfer ownership of "{orgName}"
-
+