* Update nextjs.mdx
just a little comment.. that save LOTS OF DEBUGGING time.
* fix: tweak wording
---------
Co-authored-by: Charis <26616127+charislam@users.noreply.github.com>
* feat(docs): fetch conn string
Add option to ProjectConfigVariables to fetch the Supavisor session mode connection string, for setting up MCP server
* docs(mcp): reminder to replace password placeholder in connection string
* fix: display helpful message if project paused
---------
Co-authored-by: Greg Richardson <greg.nmr@gmail.com>
* chore: document how to rollback declarative schema
* Update declarative-database-schemas.mdx
* Update declarative-database-schemas.mdx
* chore: warn about down migration
Update link to webhooks settings in edge functions example for push notifications
After the recent addition of integrations and database webhooks settings being moved to the integrations page, the link to database webhooks settings in the edge functions example for push notifications led to a 404.
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.
* fix: consistent disk unit
* Update apps/docs/content/guides/platform/manage-your-usage/disk-throughput.mdx
* Update apps/docs/content/guides/platform/manage-your-usage/disk-throughput.mdx
* Update apps/docs/content/guides/platform/manage-your-usage/disk-throughput.mdx
* docs: makes use of singular/plural for metrics that are billed hourly consistent.
* ci: Autofix updates from GitHub workflow
* fix: instance is Mbps
* fix: description Mbps
---------
Co-authored-by: Thomas <31189692+ecktoteckto@users.noreply.github.com>
Co-authored-by: github-tidy-bot <github-tidy-bot@supabase.com>
Webhooks are not firing locally unless we use `host.docker.internal` instead of `localhost`
Multiple people were encountering this issue, and it was discussed here:
https://github.com/supabase/supabase/issues/13005
Thanks!
* adds blog post and stub
* Adds dates
* adds a description
* reworking the blog
* blog og
* fix description
* updates
* adds the form
* change date
---------
Co-authored-by: Francesco Sansalvadore <f.sansalvadore@gmail.com>
TheOtherBrian1