mirror of
https://github.com/supabase/supabase.git
synced 2026-06-21 22:12:50 +08:00
Merge branch 'master' into feat/docs-v2-move-guides-to-pages-folder
This commit is contained in:
Terry Sutton
@@ -24,5 +24,5 @@ Read [this post](https://supabase.com/blog/supabase-storage) on why we decided t
|
||||
|
||||
- [Source Code](https://github.com/supabase/storage-api)
|
||||
- [Known bugs and issues](https://github.com/supabase/storage-js/issues)
|
||||
- [Storage Guides](/guides/storage)
|
||||
- [Storage Guides](/docs/guides/storage)
|
||||
- [OpenAPI Docs](https://supabase.github.io/storage-api/)
|
||||
|
||||
@@ -25,6 +25,27 @@ const nextConfig = {
|
||||
dangerouslyAllowSVG: true,
|
||||
domains: ['avatars.githubusercontent.com', 'github.com', 'user-images.githubusercontent.com'],
|
||||
},
|
||||
async headers() {
|
||||
return [
|
||||
{
|
||||
source: '/(.*)',
|
||||
headers: [
|
||||
{
|
||||
key: 'Strict-Transport-Security',
|
||||
value: '',
|
||||
},
|
||||
{
|
||||
key: 'X-Robots-Tag',
|
||||
value: 'all',
|
||||
},
|
||||
{
|
||||
key: 'X-Frame-Options',
|
||||
value: 'DENY',
|
||||
},
|
||||
],
|
||||
},
|
||||
]
|
||||
},
|
||||
}
|
||||
|
||||
// next.config.js
|
||||
|
||||
@@ -321,8 +321,8 @@ called `supabase_realtime`, and by managing this publication you can control whi
|
||||
|
||||
### Securing your Routes
|
||||
|
||||
Your API is designed to work with Postgres Row Level Security (RLS). If you use Supabase [Auth](/guides/auth), you can restrict data based on the logged-in user.
|
||||
To control access to your data, you can use [Policies](/guides/auth#policies).
|
||||
Your API is designed to work with Postgres Row Level Security (RLS). If you use Supabase [Auth](/docs/guides/auth), you can restrict data based on the logged-in user.
|
||||
To control access to your data, you can use [Policies](/docs/guides/auth#policies).
|
||||
When you create a table in Postgres, Row Level Security is disabled by default. To enable RLS:
|
||||
|
||||
<Tabs
|
||||
|
||||
@@ -45,7 +45,7 @@ git init
|
||||
supabase init
|
||||
```
|
||||
|
||||
Make sure Docker is running. The [start](/docs/reference/cli/usage#supabase-start) command uses Docker to start the Supabase [services](/architecture).
|
||||
Make sure Docker is running. The [start](/docs/reference/cli/usage#supabase-start) command uses Docker to start the Supabase [services](/docs/architecture).
|
||||
This command may take a while to run if this is the first time using the CLI.
|
||||
|
||||
```bash
|
||||
|
||||
@@ -49,7 +49,7 @@ We have exposed the audit trail directly in the dashboard, as well as the GoTrue
|
||||
|
||||
### Auth UI widget
|
||||
|
||||
In case our Auth endpoints aren't easy enough already, we've built a React [Auth Widget](http://ui.supabase.com/?path=/story/auth-auth--default) for you to drop into your app and to get up-and-running in minutes.
|
||||
In case our Auth endpoints aren't easy enough already, we've built a React [Auth Widget](https://ui.supabase.com/?path=/story/auth-auth--default) for you to drop into your app and to get up-and-running in minutes.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -32,7 +32,7 @@ Then time went on, and we started gaining traction - a lot faster than expected.
|
||||
The nice thing about building for developers is that they are very vocal about the features they want to see next.
|
||||
And so we kept shipping - a SQL editor, a Table view, User management, auto-generated Docs, and everything else you can find on the Dashboard today.
|
||||
|
||||
We've been planning to make the Dashboard public for a long time now, starting with [Supabase UI](http://ui.supabase.com/),
|
||||
We've been planning to make the Dashboard public for a long time now, starting with [Supabase UI](https://ui.supabase.com/),
|
||||
[`supabase/grid`](https://github.com/supabase/grid), and a standalone [PR](https://github.com/supabase/supabase/pull/2281) for Supabase Studio.
|
||||
But as feature requests kept rolling in it became a Sisyphean task to maintain separate code bases.
|
||||
|
||||
|
||||
@@ -179,7 +179,7 @@ If you have any questions please reach out via [Twitter](https://twitter.com/sup
|
||||
|
||||
## More Python and Supabase resources
|
||||
- [supabase-py](https://github.com/supabase-community/supabase-py)
|
||||
- [Slack Consolidate: a slackbot built with Python and Supabase](blog/slack-consolidate-slackbot-to-consolidate-messages)
|
||||
- [Slack Consolidate: a slackbot built with Python and Supabase](/blog/slack-consolidate-slackbot-to-consolidate-messages)
|
||||
- [Supabase-py (Database) on Replit](https://replit.com/@Supabase/Supabase-py-Database?v=1)
|
||||
|
||||
|
||||
|
||||
@@ -56,7 +56,7 @@ _Our limited edition swag is approved by professional swag testers like Peanut!_
|
||||
allowfullscreen
|
||||
></iframe>
|
||||
|
||||
We now have a shiny new [Launch Week page](http://supabase.com/launch-week), your one-stop shop for all things Launch Week, where you can find each day's feature as well as highlights from the past Launch Weeks.
|
||||
We now have a shiny new [Launch Week page](https://supabase.com/launch-week), your one-stop shop for all things Launch Week, where you can find each day's feature as well as highlights from the past Launch Weeks.
|
||||
|
||||
We've taken a page out of [Vercel's Virtual Events Starter Kit](https://vercel.com/templates/next.js/virtual-event-starter-kit), and generated over 3000 virtual tickets. Thank you all for participating, we love [seeing your tickets on Twitter](https://twitter.com/hashtag/SupaLaunchWeek?src=hashtag_click&f=live)! To make this work, we've adapted the Virtual Events Starter Kit and [added in a Supabase Database provider](https://github.com/vercel/virtual-event-starter-kit/pull/88) as an alternative to the Redis database option.
|
||||
|
||||
|
||||
@@ -63,7 +63,7 @@ We're making some changes to the way the Dashboard interacts with your database.
|
||||
|
||||
|
||||
|
||||
In case you missed it, Heroku is shutting down their free tier. We're big fans of Heroku and take a lot of inspiration from what they've built. Supabase is compatible with Heroku's PostgreSQL product (because we're just Postgres too), and if you have a free project running on Heroku we've created a [tool to help migrate](http://migrate.supabase.com/) to our free tier.
|
||||
In case you missed it, Heroku is shutting down their free tier. We're big fans of Heroku and take a lot of inspiration from what they've built. Supabase is compatible with Heroku's PostgreSQL product (because we're just Postgres too), and if you have a free project running on Heroku we've created a [tool to help migrate](https://migrate.supabase.com/) to our free tier.
|
||||
|
||||
## Made with Supabase
|
||||
|
||||
|
||||
Reference in New Issue
Block a user