-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Document new package for Supabase JS
- Loading branch information
Showing
6 changed files
with
119 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,99 @@ | ||
--- | ||
title: Bemi Supabase JS Integration - Automate Context-Aware Audit Trails with PostgreSQL | ||
sidebar_label: Supabase JS | ||
hide_title: true | ||
description: Discover how Bemi integrates with Supabase JS and PostgreSQL to automatically track database changes, providing robust audit trails for your applications. Learn how to install and use the Bemi Supabase JS package for enhanced data tracking. | ||
image: 'img/social-card.png' | ||
keywords: [Bemi, Supabase, PostgreSQL, database auditing, data tracking, context-aware audit, application context, audit log, audit trail, data versioning] | ||
--- | ||
|
||
# Supabase JS | ||
|
||
<a class="github-button" href="https://github.com/BemiHQ/bemi-supabase-js" data-size="large" data-show-count="true" aria-label="Star BemiHQ/bemi-supabase-js on GitHub">BemiHQ/bemi-supabase-js</a> | ||
<br /> | ||
<br /> | ||
|
||
[Bemi](https://bemi.io) plugs into [Supabase JS](https://github.com/supabase/supabase-js) and PostgreSQL to track database changes automatically. It unlocks robust context-aware audit trails and time travel querying inside your application. | ||
|
||
This package is a recommended Supabase JS integration, enabling you to pass application-specific context when performing database changes. This can include context such as the 'where' (API endpoint, worker, etc.), 'who' (user, cron job, etc.), and 'how' behind a change, thereby enriching the information captured by Bemi. | ||
|
||
See this [example repo](https://github.com/BemiHQ/bemi-supabase-js-example) as an Todo app example with Supabase JS that automatically tracks and contextualizes all changes. | ||
|
||
## Prerequisites | ||
|
||
- Supabase JS | ||
|
||
## Installation | ||
|
||
1. Install the NPM package | ||
|
||
```sh | ||
npm install @bemi-db/supabase-js | ||
``` | ||
|
||
2. Generate a Supabase JS migration file to add a [Database Function](https://supabase.com/docs/guides/database/functions) for passing application context with all data changes into PostgreSQL replication log | ||
|
||
```sh | ||
npx bemi migration new | ||
``` | ||
|
||
3. Run the Supabase JS migration | ||
|
||
```sh | ||
npx supabase migration up | ||
``` | ||
|
||
## Usage | ||
|
||
Now you can easily specify custom application context that will be automatically passed with all data changes by calling `setContext` in your [Supabase Edge Function](https://supabase.com/docs/guides/functions): | ||
|
||
```ts | ||
import { setContext } from 'https://esm.sh/@bemi-db/[email protected]' | ||
import { createClient } from 'https://esm.sh/@supabase/[email protected]' | ||
|
||
Deno.serve(async (req) => { | ||
const supabase = createClient(...) | ||
const { method, url } = req | ||
const endpoint = `/${url.split('/')[3]}` | ||
const payload = method === 'POST' ? await req.json() : {} | ||
|
||
// Customizable context | ||
await setContext(supabase, { method, endpoint, payload }) | ||
|
||
// Your code that performs data changes | ||
}) | ||
``` | ||
|
||
|
||
Application context: | ||
|
||
* Is bound to the current database session within an HTTP request. | ||
* Is used only with `INSERT`, `UPDATE`, `DELETE` SQL queries performed via Supabase JS. | ||
* Is passed directly into PG [Write-Ahead Log](https://www.postgresql.org/docs/current/wal-intro.html) with data changes without affecting the structure of the database and SQL queries. | ||
|
||
## Database connection | ||
|
||
Connect your PostgreSQL source database on [bemi.io](https://bemi.io) to start ingesting and storing all data changes stitched together with application-specific context. The database connection details can be securely configured through the [dashboard UI](https://dashboard.bemi.io/log-in?ref=supabase-js) in a few seconds. | ||
|
||
![dashboard](/img/dashboard.png) | ||
|
||
Once your destination PostgreSQL database has been fully provisioned, you'll see a "Connected" status. You can now test the connection after making database changes in your connected source database: | ||
|
||
``` | ||
psql postgres://[USERNAME]:[PASSWORD]@[HOSTNAME]:5432/[DATABASE] -c 'SELECT "primary_key", "table", "operation", "before", "after", "context", "committed_at" FROM changes;' | ||
primary_key | table | operation | before | after | context | committed_at | ||
-------------+-------+-----------+---------------------------------------------------+----------------------------------------------------+-----------------------------------------------------------------------------------------------+------------------------ | ||
26 | todo | CREATE | {} | {"id": 26, "task": "Sleep", "isCompleted": false} | {"method": "POST", "endpoint": "/todos", "payload": {"task": "Sleep", "isCompleted": false} | 2023-12-11 17:09:09+00 | ||
27 | todo | CREATE | {} | {"id": 27, "task": "Eat", "isCompleted": false} | {"method": "POST", "endpoint": "/todos", "payload": {"task": "Eat", "isCompleted": false}} | 2023-12-11 17:09:11+00 | ||
28 | todo | CREATE | {} | {"id": 28, "task": "Repeat", "isCompleted": false} | {"method": "POST", "endpoint": "/todos", "payload": {"task": "Repeat", "isCompleted": false}} | 2023-12-11 17:09:13+00 | ||
26 | todo | UPDATE | {"id": 26, "task": "Sleep", "isCompleted": false} | {"id": 26, "task": "Sleep", "isCompleted": true} | {"method": "PUT", "endpoint": "/todos/26/complete", "payload": {}} | 2023-12-11 17:09:15+00 | ||
27 | todo | DELETE | {"id": 27, "task": "Eat", "isCompleted": false} | {} | {"method": "DELETE", "endpoint": "/todos/27", "payload": {}} | 2023-12-11 17:09:18+00 | ||
``` | ||
|
||
See [Destination Database](/postgresql/destination-database) for more details. | ||
|
||
## License | ||
|
||
Distributed under the terms of the [LGPL-3.0](https://github.com/BemiHQ/bemi-supabase-js/blob/main/LICENSE). | ||
If you need to modify and distribute the code, please release it to contribute back to the open-source community. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters