Connect and play with Supabase REST API / Graphql easily
Free • Open Source
View Demo
·
Report Bug
·
Request Feature
- 🤩 Free
- 🚀 Unlimited API Request
- 🎨 Alowed to use on other project
This is my Supabase Bring the Func(🕺) Hackathon 2022 submission!
SupaDB allows user that wanted to play with Supabase REST API/Grahql easily without having to manually seed the database.
SupaDB also allows Frontend Developer that wanted to focus on design to easily fetch the data without worrying about CORS stuff.
- CRON Job by GitHub action
- Vercel Serverless to scrap data
- Upsert data into Supabase Database
- Create custom secret for every user
create or replace function generate_secret ()
returns text
language plpgsql
as
$$
begin
return substr(md5(random()::text), 0, 25);
end;
$$-
Wrap the secret in JWT token, set as Authorization Key in header
-
RLS to verify secret token exist in request
create or replace function auth.verify() returns text as $$
select coalesce(
nullif(current_setting('request.jwt.claim.secret', true), ''),
nullif(current_setting('request.jwt.claims', true), '')::jsonb ->> 'secret'
)::text
$$ language sql stable;In order to monitor the API usage, I created a temporary scripts to Insert Log data to a custom table
- Create Foreign Data Wrapper sing
file_fdw(GitHub discussion)
CREATE EXTENSION file_fdw;
CREATE SERVER logserver FOREIGN DATA WRAPPER file_fdw;
CREATE FOREIGN TABLE pglog (
log_time timestamp(3) with time zone,
user_name text,
database_name text,
process_id integer,
connection_from text,
session_id text,
session_line_num bigint,
command_tag text,
session_start_time timestamp with time zone,
virtual_transaction_id text,
transaction_id bigint,
error_severity text,
sql_state_code text,
message text,
detail text,
hint text,
internal_query text,
internal_query_pos integer,
context text,
query text,
query_pos integer,
location text,
application_name text,
backend_type text,
leader_pid integer,
query_id bigint
) SERVER logserver
OPTIONS ( filename '/var/log/postgresql/postgresql.csv', format 'csv' );- Query data from
pglogforeign table created in step 1.
select * from
(select
concat(session_id, process_id, virtual_transaction_id) as id,
btrim(split_part(detail, ', ', 8), '$6= ''""')::json ->> 'secret' as secret,
btrim(split_part(detail, ', ', 12), '$10= /''' ) as table,
log_time as created_at
from pglog where command_tag ~ 'SELECT' and message ~* 'execute 1'
) as T
where T.table <> 'buckets'- Setup CRON job to insert above query to table
select
cron.schedule(
'save-logfile', -- name of the cron job
'*/3 * * * *', -- every 3 minutes
$$
insert into history (id, secret, ref, created_at)
(/* step 2 */)
on conflict (id)
do nothing;
$$
);- Create view for easy monitor
create or replace view api_history
as select u.id as id, count(*) as count from
(select h.*, s.user_id from public.history h
left join public.secrets s on h.secret = s.secret
where h.secret is not null and h.created_at >= now() - interval '1 day'
) a
left join auth.users u on a.user_id = u.id
group by u.idYarn
-
npm install --global yarn vercel
- Clone the repo
git clone https://github.com/zernonia/supadb.git
- Install NPM packages
cd supadb yarn install - Run local Vercel development instance
vercel dev
Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/AmazingFeature) - Commit your Changes (
git commit -m 'Add some AmazingFeature') - Push to the Branch (
git push origin feature/AmazingFeature) - Open a Pull Request
Not Associated with Supabase.
Distributed under the MIT License. See LICENSE for more information.
Zernonia - @zernonia - [email protected]
Also, if you like my work, please buy me a coffee ☕😳
