Rotimi Best
c7854efae3
* feat: new components, deploy storybook * refactor: simplify component field definitions and enhance button loading state - Removed unnecessary type imports and simplified the FIELDS array definitions across multiple components in Storybook. - Updated button component to use a loading state instead of isLoading, improving clarity and consistency in props. - Adjusted button stories to reflect the new loading prop and enhanced the button's loading visual feedback. - Minor CSS adjustments for better layout and styling consistency. * chore: add field, card, password components * feat: improve page component & update AuthUI path * chore: update bits-ui to version 2.14.4 and all org related UI's - Updated bits-ui dependency in pnpm-lock.yaml and package.json to version 2.14.4. - Refactored imports for RoleBasedSecurity and UpgradeBanner components to use the new ui feature directory. - Removed unused Course components and related files to clean up the codebase. - Enhanced various components to improve consistency and maintainability. * chore: move all setting buttons to the top and update auth ui styles * chore: remove svelte-loading-spinners and replace with @cio/ui/base/spinner - Removed all instances of svelte-loading-spinners from the project. - Updated components to use the new Spinner from @cio/ui/base/spinner. - Cleaned up pnpm-lock.yaml and package.json to reflect the removal of svelte-loading-spinners. - Added new CSS animations for rocket launch effects in app.css. - Enhanced email change flow with updated verification messages in translations. * chore: remove supabase file upload from dashboard and move to r2 * chore: update organization API and UI components - Added new API methods for organization plan operations and team management. - Introduced middleware for API key authentication and organization admin checks. - Refactored organization-related components to utilize the new API structure. - Updated various UI components to improve consistency and maintainability. - Enhanced error handling and validation for organization-related actions. - Removed deprecated services and streamlined the codebase.
46 lines
1.9 KiB
Markdown
46 lines
1.9 KiB
Markdown
# @cio/db
|
|
|
|
This package handles everything related to the database, schema, migrations and connection.
|
|
|
|
## Stack
|
|
|
|
1. Postgres - We use postgres for the database
|
|
2. Drizzle ORM - For managing and querying the database
|
|
3. Better Auth - For managing the auth tables (users, account, session).
|
|
|
|
## Workflow
|
|
|
|
We used Supabase in the past for managing the supabase but have now moved on to use postgres directly and auth managed by our backend. This means the workflow is a mix of the Database First approach (Option 1) and the Codebase First approach (Option 2). Learn more about each approach [from the drizzle migration docs](https://orm.drizzle.team/docs/migrations).
|
|
|
|
Here is how I do it:
|
|
|
|
### 1. Local DB to Drizzle Schema TS file
|
|
|
|
I have a postgres tool where I can make changes to the db as I want. I am not so familiar with drizzle that much so I am sticking with this for now.
|
|
|
|
```bash
|
|
pnpm db pull # this does sql -> drizzle ts code
|
|
```
|
|
|
|
### 2. Drizzle Schema file to Prod SQL
|
|
|
|
Now when I am ready to deploy the feature, I can use [option 2](https://orm.drizzle.team/docs/migrations) which is makes the typescript schema the source of truth. This command will only run on CI on every merge on a condition that there was a change to the schema file `packages/db/src/schema.ts`
|
|
|
|
```bash
|
|
pnpm db push # this does drizzle ts code to prod db
|
|
```
|
|
|
|
## OR
|
|
|
|
I can make changes directly to the schema file and run `pnpm db push` to push the changes to the source db.
|
|
|
|
## Change email flow
|
|
|
|
1. User changes email on dashboard to new email
|
|
2. We send an email verification to the current, permitting the change
|
|
3. Meanwhile the frontend reverts to the previous email.
|
|
4. User clicks approve link in email
|
|
5. User is redirected to settings page with message that another email has been sent to the new email
|
|
6. User goes to new email inbox and clicks approve link in email
|
|
7. User is taken to the settings page with new email address.
|