From fd19371efc34605cfca9783e59e2d3733b56dbd6 Mon Sep 17 00:00:00 2001 From: Qiao Han Date: Sat, 8 Jul 2023 13:40:51 +0800 Subject: [PATCH] chore(docs): update local logflare setup requirements --- apps/docs/pages/guides/getting-started/local-development.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/apps/docs/pages/guides/getting-started/local-development.mdx b/apps/docs/pages/guides/getting-started/local-development.mdx index 07f364c69de..76a50025ea1 100644 --- a/apps/docs/pages/guides/getting-started/local-development.mdx +++ b/apps/docs/pages/guides/getting-started/local-development.mdx @@ -429,7 +429,8 @@ For these changes to take effect, you need to run `supabase stop` and `supabase Local logs rely on the Supabase Analytics Server. This can be enabled via the CLI configuration, and requires a Google Cloud project and BigQuery access. - The Google Cloud project must have billing enabled. Read more about this requirement + The Google Cloud project must have billing enabled. Its dataset location must also be in the US. + Read more about this requirement [here](https://supabase.com/docs/reference/self-hosting-analytics/introduction#bigquery).