-
Notifications
You must be signed in to change notification settings - Fork 190
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
feat: store deployed databases info in Supabase DB #31
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really great work @jgoux 🎉
success: false, | ||
error: "You can't deploy a database that is bigger than 100MB", | ||
}, | ||
{ status: 413 } | ||
) | ||
} | ||
|
||
const databaseId = params.id | ||
const key = `dbs/${databaseId}.tar.gz` | ||
|
||
const gzip = createGzip() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed that sometimes PGlite produced a non-gzipped tar file (not sure what caused this). Should we try to detect this somehow or check mime type?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my case it's the opposite, I never had PGlite produce a gzipped tarball, that's why I gzip it in the route here.
Should we ping Sam about it?
Here are the main changes:
sidebar.tsx
into multiple components so it's more manageabledeployed_databases
table in Supabase database to store the deployed databases infos