Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Supabase - Storage + DB #43

Open
1 of 2 tasks
Tracked by #20
amandesai01 opened this issue Aug 4, 2024 · 10 comments
Open
1 of 2 tasks
Tracked by #20

Supabase - Storage + DB #43

amandesai01 opened this issue Aug 4, 2024 · 10 comments

Comments

@amandesai01
Copy link
Member

amandesai01 commented Aug 4, 2024

@Nilakshhh
Copy link

hey @amandesai01 can I work on this?

@harshil15999
Copy link
Contributor

harshil15999 commented Aug 4, 2024

hey @amandesai01 can I work on this?

Hi can you telll what approach will you be taking in this ? @Nilakshhh

@harshil15999
Copy link
Contributor

  • Write a unstorage driver to connect to supabase storage and save data there.
  1. Refer to https://github.com/profilecity/unstorage-s3-driver for writing an unstorage driver for supabase . By storage we mean blob storage

@harshil15999
Copy link
Contributor

@amandesai01 please split this issue into two sub tasks

@Nilakshhh
Copy link

Nilakshhh commented Aug 4, 2024

@harshil15999
The objective is to create a custom 'unstorage' driver that can interact with supabase and perform necessary CRUD operations on a POSTGRES database
We would require to import @supabase/supabase-js library and 'unstorage' to create a custom driver, ofetch is not necessary because supabase can handle HTTP requests.

Driver options required are URL, API_KEY and storage bucket name.
Basic CRUD operations in my opinion should be
-getItem
-setItem
-getAllItems
-removeItem
-clearAllItems

After the normalization of API_KEY, we can use our driver to connect to Supabase and handle database operations.

Please guide me if there should be any changes in the approach

@vaswanid
Copy link

vaswanid commented Aug 5, 2024

Can I work on this issue?

@harshil15999
Copy link
Contributor

Can I work on this issue?

what part of this issue you want to work with. Can you come with one line of proposal.

@harshil15999
Copy link
Contributor

@harshil15999 The objective is to create a custom 'unstorage' driver that can interact with supabase and perform necessary CRUD operations on a POSTGRES database We would require to import @supabase/supabase-js library and 'unstorage' to create a custom driver, ofetch is not necessary because supabase can handle HTTP requests.

Driver options required are URL, API_KEY and storage bucket name. Basic CRUD operations in my opinion should be -getItem -setItem -getAllItems -removeItem -clearAllItems

After the normalization of API_KEY, we can use our driver to connect to Supabase and handle database operations.

Please guide me if there should be any changes in the approach

Issue is divided into two parts.

  1. Making a driver for storage . by storage I mean something similar to s3
  2. Second part is testing whether drizzle can be used to store things in supabase

@harshil15999
Copy link
Contributor

@harshil15999 The objective is to create a custom 'unstorage' driver that can interact with supabase and perform necessary CRUD operations on a POSTGRES database We would require to import @supabase/supabase-js library and 'unstorage' to create a custom driver, ofetch is not necessary because supabase can handle HTTP requests.

Driver options required are URL, API_KEY and storage bucket name. Basic CRUD operations in my opinion should be -getItem -setItem -getAllItems -removeItem -clearAllItems

After the normalization of API_KEY, we can use our driver to connect to Supabase and handle database operations.

Please guide me if there should be any changes in the approach

Decide whether you wanna work with storage or database .

@gloriasingh08
Copy link

Can I work on this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants