Doriel Rivalet DorielRivalet

Bridging External Auth with Supabase User Impersonation

As promised, here’s a write up on how I integrated Clerk authentication with Supabase Studio’s user impersonation feature for local development. I drafted it as a mini “how-to” guide, and while writing it, I realized there might be a simpler solution on Supabase’s end to handle this more gracefully...more on that at the end! 😀

This gist is split into two main sections:

Section 1: A guide to bridging Clerk and Supabase Studio impersonation locally
Section 2: A proposed enhancement to Supabase Studio's impersonation mode to more elegantly solve the same problem for all environments

Section 1: A Guide to Bridging Clerk and Supabase Studio Impersonation Locally

Supabase RLS Policy functions and Postgres transaction configuration association

source

Supabase's RLS Policy functions	PgTransaction config to set	Description
`auth.uid()`	`set_config('request.jwt.claim.sub', <current_user_uid>, true)`	`<current_user_uid>` comes from your own way to get the current user uid
`auth.email()`	`set_config('request.jwt.claim.email', <current_user_email>, true)`	`<current_user_email>` The current user email
`auth.role()`	`set_config('request.jwt.claim.role', <current_user_role>, true)`	`<current_user_role>` The current user role
`auth.jwt()`	`set_config('request.jwt.claim', <current_user_jwt>, true)`	`<current_user_jwt>` The current user jwt token. 🚨 I'm note sure about the config name, found nothing in Supabase repo

This gist was partially inspired by this blog about Next.js Vercel CI with GitHub actions.

The problem

An easy way to deploy and host websites for free is to use GitHub pages. If you've deployed a Next.js project to GitHub pages, you may have used a GitHub action similar to this in the past to automatically redeploy the site when a new commit is pushed:

# gh-pages-merge.yml
name: Deploy to gh-pages on merge
on:
  push:

Directory structure:

.
├── papers
│   ├── Title - Author.pdf
│   └── Title - Author.pdf
├── notes
│   ├── 2022-04-10
│   │   ├── note.tex

ReadValue<T>, ReadString, ReadPointer: https://github.com/LiveSplit/LiveSplit/blob/master/LiveSplit/LiveSplit.Core/ComponentUtil/ProcessExtensions.cs

// "address" is an IntPtr to an int value
int intValue = game.ReadValue<int>(address);

// "address" is an IntPtr to a string, "64" is the maximum amount of bytes to read
string strValue = game.ReadString(address, 64);

// "address" is an IntPtr to another address (for example a class)
IntPtr ptrValue = game.ReadPointer(address);

How to setup a literally free CDN

Create repo on GitHub where you'll put your files.
Use jsDeliver or statically to get your assets.

Here is repo I'm using:

https://github.com/jcubic/static

And links to files look like this:

By default, <ItemsControl>/<ScrollViewer> doesn't use virtualization. All its items are rendered at once. This causes lags/freezing on first render and each re-render (for example, if list data or window size changes).

Adding ScrollViewer.CanContentScroll="True" will enable virtualization and make loading fast. But the list will be scrolled one whole item a time, which feels like jumping if items height is big enough.

To make virtualization enabled and keep smooth scrolling, add also VirtualizingPanel.ScrollUnit="Pixel"

	import { and, type DBQueryConfig, eq, type SQLWrapper } from "drizzle-orm";
	import { drizzle } from "drizzle-orm/postgres-js";
	import postgres, { type Sql } from "postgres";

	import { type AnyArgs } from "@/common";

	import {
	type DbClient,
	type DbTable,
	type DeleteArgs,

	/**
	* USERS
	* Note: This table contains user data. Users should only be able to view and update their own data.
	* Some data is synced back and forth to `auth.users` as described below.
	*
	* `full_name`: synced in both directions
	* `email`: synced from user metadata to profile only
	* `avatar_url`: synced from user metadata to profile only
	* `terms_accepted_at`: synced from profile to user metadata only
	*/

	import { PrismaClient } from '@prisma/client';
	import type { User } from '@prisma/client';
	import { createPool, sql } from 'slonik';

	export const buildBaseConnectionURL = (config) => {
	return (
	'postgresql://' +
	config.DB_USER +
	':' +
	config.DB_PASS +