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>
* feat: add SOC 2 page to docs
* feat: more linking
* fix: make linters happy
* fix: prettier
* chore: make security page available
* typo: sp
* publish security
* chore: publish new security section
* change mobile menu to show Security on Security section
---------
Co-authored-by: Charis Lam <26616127+charislam@users.noreply.github.com>
Type docs pulled from JS client libraries were expected to be in version 0.22, which unfortunately is a bit old and incompatible with TypeScript 5. Therefore any JS lib that upgrades their toolchian to TS 5 will inadvertently break their type specs in docs.
This PR updates docs to also support 0.27 (the latest stable version, compatible with TS 5), in addition to the old version. Parallel support is required since many libs are still on the old version.
The main changes are:
- The comment shape has changed in typedoc.
- kindString has been deprecated in favor the kind numbers.
- indexSignatures are now plural (an array).
* Add a note that schema needs to exist on Supabase before running
migrate. Otherwise one will receivie a following error
$ php artisan migrate
INFO Preparing database.
Creating migration table ........................................................................................................... 599.73ms FAIL
Illuminate\Database\QueryException
SQLSTATE[3F000]: Invalid schema name: 7 ERROR: no schema has been selected to create in at character 14 (Connection: pgsql, SQL: create table "migrations" ("id" serial not null
primary key, "migration" varchar(255) not null, "batch" integer not null))
at vendor/laravel/framework/src/Illuminate/Database/Connection.php:823
819▕ $this->getName(), $query, $this->prepareBindings($bindings), $e
820▕ );
821▕ }
822▕
➜ 823▕ throw new QueryException(
824▕ $this->getName(), $query, $this->prepareBindings($bindings), $e
825▕ );
826▕ }
827▕ }
+41 vendor frames
42 artisan:16
Illuminate\Foundation\Application::handleCommand()
* Apply suggestions from code review
---------
Co-authored-by: Vladimir Vuksan <vuksan-github@vuksan.com>
Co-authored-by: Charis <26616127+charislam@users.noreply.github.com>
* Consolidate different versions of postcss. Remove @mertasan/tailwindcss-variables from ui package.
* Bump vitest in pg-meta to remove a vulnerable version of vite.
* Bump dompurify.
* Bump all octokit deps to solve 2 vulns.
* Fix warnings about destructuring json imports.
* Remove a console.log in docs.
* Fix the changelog page to use an ESM import.
* Stabilize the generate-sitemap script output.
* Try another fix for the changelog.
* fixed docs bug: when importing wasm, you need to include the js and use this. Otherwise, there will be wasm instantiate errors
* Update wasm.mdx
Got rid of filename on top of markdown
* Update index.ts
got rid of filename comment at the top
invalid cliam: missing sub seems to (also?) be returned as a 403, not a 401. Discovered this when I was testing something else, so updating the troubleshooting guide for it.
* feat: llms.txt
* feat: split llms.txt into multiple files
We have too many docs, so the concatenated text file uses an unreasonable amount of tokens. Chunk it up a little so it's more usable.
Ziinc