dima/supabase
1
0 Fork 0
mirror of https://github.com/supabase/supabase.git synced 2026-10-10 20:05:06 +03:00
Code Issues Packages Projects Releases Wiki Activity

Add docker compose command

Browse Source
This commit is contained in:
Chase Granberry committed 2023-03-28 15:33:20 -07:00
1 parent 2d7b9d843b
commit 049c88f6ed
1 file changed
+7 -2
Download Patch File Download Diff File Expand all files Collapse all files
apps/docs/docs/ref/self-hosting-analytics/introduction.mdx
+7 -2
View File
@@ -18,13 +18,18 @@ The Supabase Analytics server (Logflare) manages the ingest and query pipelines
Deployed in a self-hosted environment, with the exception of API edge logs, all logs and views supported by Logflare should match the Supabase Cloud.
All logs are routed to Logflare via Vector. Kong routes API requests to PostgREST so self-hosted or local deployments will use Kong request logs instead of the Supabase Cloud API gateway.
All logs are routed to Logflare via Vector. Kong routes API reque`sts to PostgREST so self-hosted or local deployments will use Kong request logs instead of the Supabase Cloud API gateway.
There will be some differences in the log event payloads with self-hosted API requests vs requests handled by the Supbase Cloud API gateway.
### Docker Compose
If you're self-hosting a production application with the Supabase stack and want to use the Analytics server pull in the separate Docker compose.
To start the whole Supabase stack with the Analytics server run:
```bash
cd docker
docker compose -f docker-compose-logging.yml up
```
</RefSubLayout.Details>