mirror of
https://github.com/supabase/supabase.git
synced 2026-05-28 00:16:46 +08:00
2709fa4a3e
Partials are currently defined via MDX includes. This PR switches to pre-compile-time partials, which have a new syntax: ``` <$Partial path="path/to/file.mdx" /> ``` ## Rationale This produces two improvements: 1. Partial substitution can occur in pipelines that don't use MDX compilation. For example, we can now do partial substitution before building the search index, so partial content will also be indexed. 2. After the App Router migration, the MDXProviders should've been deprecated, but were kept around for the sole reason of making partials work, and leading to us shipping unnecessary client-side code. We get a minor decrease in overall client bundle size (5.74 MB to 5.6 MB) by getting rid of the Providers. ## Breaking changes Besides the change to partial syntax, the arguments are also less powerful than before because we are doing string substitution and don't have the full power of JS. Defining string variables is still possible (documented in the Contributing guide), and since that's all we actually do in practice, this shouldn't be too cumbersome. There is always the escape hatch of making a custom component for more complex content reuse cases.
65 lines
2.0 KiB
Plaintext
65 lines
2.0 KiB
Plaintext
## Project setup
|
|
|
|
Before we start building we're going to set up our Database and API. This is as simple as starting a new Project in Supabase and then creating a "schema" inside the database.
|
|
|
|
### Create a project
|
|
|
|
1. [Create a new project](https://supabase.com/dashboard) in the Supabase Dashboard.
|
|
1. Enter your project details.
|
|
1. Wait for the new database to launch.
|
|
|
|
### Set up the database schema
|
|
|
|
Now we are going to set up the database schema. We can use the "User Management Starter" quickstart in the SQL Editor, or you can just copy/paste the SQL from below and run it yourself.
|
|
|
|
<Tabs
|
|
scrollable
|
|
size="small"
|
|
type="underlined"
|
|
defaultActiveId="dashboard"
|
|
queryGroup="database-method"
|
|
>
|
|
<TabPanel id="dashboard" label="Dashboard">
|
|
|
|
1. Go to the [SQL Editor](https://supabase.com/dashboard/project/_/sql) page in the Dashboard.
|
|
2. Click **User Management Starter**.
|
|
3. Click **Run**.
|
|
|
|
<Admonition type="note">
|
|
|
|
You can pull the database schema down to your local project by running the `db pull` command. Read the [local development docs](/docs/guides/cli/local-development#link-your-project) for detailed instructions.
|
|
|
|
</Admonition>
|
|
|
|
```bash
|
|
supabase link --project-ref <project-id>
|
|
# You can get <project-id> from your project's dashboard URL: https://supabase.com/dashboard/project/<project-id>
|
|
supabase db pull
|
|
```
|
|
|
|
</TabPanel>
|
|
<TabPanel id="sql" label="SQL">
|
|
|
|
<Admonition type="note">
|
|
|
|
When working locally you can run the following command to create a new migration file:
|
|
|
|
</Admonition>
|
|
|
|
```bash
|
|
supabase migration new user_management_starter
|
|
```
|
|
|
|
<$Partial path="user_management_quickstart_sql_template.mdx" />
|
|
|
|
</TabPanel>
|
|
</Tabs>
|
|
|
|
### Get the API keys
|
|
|
|
Now that you've created some database tables, you are ready to insert data using the auto-generated API.
|
|
We just need to get the Project URL and `anon` key from the API settings.
|
|
|
|
1. Go to the [API Settings](https://supabase.com/dashboard/project/_/settings/api) page in the Dashboard.
|
|
1. Find your Project `URL`, `anon`, and `service_role` keys on this page.
|