The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.
TypeScript aialternativeauthdatabasedenoembeddingsexamplefirebasenextjsoauth2pgvectorpostgispostgrespostgresqlpostgrestrealtimesupabasevectorswebsockets
fix: do not expose analytics by default
Andrey A.f24df26d7b35
diff --git a/docker/docker-compose.yml b/docker/docker-compose.ymlindex 6fd37691c2d..677d5ff63c2 100644--- a/docker/docker-compose.yml+++ b/docker/docker-compose.yml@@ -356,8 +356,8 @@ services:container_name: supabase-analyticsimage: supabase/logflare:1.30.3restart: unless-stopped- ports:- - 4000:4000+ # ports:+ # - 4000:4000# Uncomment to use Big Query backend for analytics# volumes:# - type: binddiff --git a/docker/volumes/api/kong.yml b/docker/volumes/api/kong.ymlindex 7441cd31285..ae69cec2824 100644--- a/docker/volumes/api/kong.yml+++ b/docker/volumes/api/kong.yml@@ -197,29 +197,29 @@ services:- name: cors## Analytics routes- - name: analytics-v1-api- _comment: 'Analytics: /analytics/v1/api/endpoints/* -> http://logflare:4000/api/endpoints/*'- url: http://analytics:4000/api/endpoints- routes:- - name: analytics-v1-api- strip_path: true- paths:- - /analytics/v1/api/endpoints/-- # auth on analytics dashboard- - name: analytics-v1- _comment: 'Analytics: /analytics/v1/* -> http://logflare:4000/*'- url: http://analytics:4000/- routes:- - name: dashboard-v1-all- strip_path: true- paths:- - /analytics/v1- plugins:- - name: cors- - name: basic-auth- config:- hide_credentials: true+ ## Not used - Studio and Vector talk directly to analytics via Docker networking.+ ## If external access is needed, add routes with key-auth matching Logflare's x-api-key auth.+ # - name: analytics-v1-api+ # _comment: 'Analytics: /analytics/v1/api/endpoints/* -> http://logflare:4000/api/endpoints/*'+ # url: http://analytics:4000/api/endpoints+ # routes:+ # - name: analytics-v1-api+ # strip_path: true+ # paths:+ # - /analytics/v1/api/endpoints/+ # - name: analytics-v1+ # _comment: 'Analytics: /analytics/v1/* -> http://logflare:4000/*'+ # url: http://analytics:4000/+ # routes:+ # - name: dashboard-v1-all+ # strip_path: true+ # paths:+ # - /analytics/v1+ # plugins:+ # - name: cors+ # - name: basic-auth+ # config:+ # hide_credentials: true## Secure Database routes- name: metadiff --git a/docker/volumes/logs/vector.yml b/docker/volumes/logs/vector.ymlindex e79d7e82685..989e250f878 100644--- a/docker/volumes/logs/vector.yml+++ b/docker/volumes/logs/vector.yml@@ -177,7 +177,8 @@ sinks:codec: 'json'method: 'post'request:- retry_max_duration_secs: 10+ retry_max_duration_secs: 30+ retry_initial_backoff_secs: 1headers:x-api-key: ${LOGFLARE_PUBLIC_ACCESS_TOKEN?LOGFLARE_PUBLIC_ACCESS_TOKEN is required}uri: 'http://analytics:4000/api/logs?source_name=gotrue.logs.prod'@@ -189,7 +190,8 @@ sinks:codec: 'json'method: 'post'request:- retry_max_duration_secs: 10+ retry_max_duration_secs: 30+ retry_initial_backoff_secs: 1headers:x-api-key: ${LOGFLARE_PUBLIC_ACCESS_TOKEN?LOGFLARE_PUBLIC_ACCESS_TOKEN is required}uri: 'http://analytics:4000/api/logs?source_name=realtime.logs.prod'@@ -201,7 +203,8 @@ sinks:codec: 'json'method: 'post'request:- retry_max_duration_secs: 10+ retry_max_duration_secs: 30+ retry_initial_backoff_secs: 1headers:x-api-key: ${LOGFLARE_PUBLIC_ACCESS_TOKEN?LOGFLARE_PUBLIC_ACCESS_TOKEN is required}uri: 'http://analytics:4000/api/logs?source_name=postgREST.logs.prod'@@ -213,13 +216,13 @@ sinks:codec: 'json'method: 'post'request:- retry_max_duration_secs: 10+ retry_max_duration_secs: 30+ retry_initial_backoff_secs: 1headers:x-api-key: ${LOGFLARE_PUBLIC_ACCESS_TOKEN?LOGFLARE_PUBLIC_ACCESS_TOKEN is required}- # We must route the sink through kong because ingesting logs before logflare is fully initialised will- # lead to broken queries from studio. This works by the assumption that containers are started in the- # following order: vector > db > logflare > kong- uri: 'http://kong:8000/analytics/v1/api/logs?source_name=postgres.logs'+ # Route directly to analytics like other sinks. Retry handles the startup+ # race where analytics may not be ready yet when early DB logs arrive.+ uri: 'http://analytics:4000/api/logs?source_name=postgres.logs'logflare_functions:type: 'http'inputs:@@ -228,7 +231,8 @@ sinks:codec: 'json'method: 'post'request:- retry_max_duration_secs: 10+ retry_max_duration_secs: 30+ retry_initial_backoff_secs: 1headers:x-api-key: ${LOGFLARE_PUBLIC_ACCESS_TOKEN?LOGFLARE_PUBLIC_ACCESS_TOKEN is required}uri: 'http://analytics:4000/api/logs?source_name=deno-relay-logs'@@ -240,7 +244,8 @@ sinks:codec: 'json'method: 'post'request:- retry_max_duration_secs: 10+ retry_max_duration_secs: 30+ retry_initial_backoff_secs: 1headers:x-api-key: ${LOGFLARE_PUBLIC_ACCESS_TOKEN?LOGFLARE_PUBLIC_ACCESS_TOKEN is required}uri: 'http://analytics:4000/api/logs?source_name=storage.logs.prod.2'@@ -253,7 +258,8 @@ sinks:codec: 'json'method: 'post'request:- retry_max_duration_secs: 10+ retry_max_duration_secs: 30+ retry_initial_backoff_secs: 1headers:x-api-key: ${LOGFLARE_PUBLIC_ACCESS_TOKEN?LOGFLARE_PUBLIC_ACCESS_TOKEN is required}uri: 'http://analytics:4000/api/logs?source_name=cloudflare.logs.prod'