From 7fb7ac5c41849c3975d3cb7bf6411e30fb9360b2 Mon Sep 17 00:00:00 2001 From: TzeYiing Date: Fri, 11 Aug 2023 18:48:50 +0800 Subject: [PATCH] chore: prettier --- apps/docs/pages/guides/cli/local-development.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/apps/docs/pages/guides/cli/local-development.mdx b/apps/docs/pages/guides/cli/local-development.mdx index 161d08a73e1..2ca4caf7dfd 100644 --- a/apps/docs/pages/guides/cli/local-development.mdx +++ b/apps/docs/pages/guides/cli/local-development.mdx @@ -428,7 +428,9 @@ supabase db remote commit --schema auth Local logs rely on the Supabase Analytics Server, and are available in the Studio automatically. - For advanced logs analysis using the Logs Explorer, it is advised to use the BigQuery backend instead of the default Postgres backend. Read about the steps [here](https://supabase.com/docs/reference/self-hosting-analytics/introduction#bigquery). + For advanced logs analysis using the Logs Explorer, it is advised to use the BigQuery backend + instead of the default Postgres backend. Read about the steps + [here](https://supabase.com/docs/reference/self-hosting-analytics/introduction#bigquery). Logs will be directed to the Analytics server instead of the docker logging driver. All logs will be stored in the local database under the `_analytics` schema.