prehistoric-systems/coolify
1
0
Fork 0
mirror of https://github.com/coollabsio/coolify.git synced 2026-03-11 08:55:47 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

fix: use separate secret for Logflare private access token

Browse source 
Using the same secret for both LOGFLARE_PUBLIC_ACCESS_TOKEN and
LOGFLARE_PRIVATE_ACCESS_TOKEN causes Supabase Studio logs to return
401 Unauthorized. Logflare requires the private token to have
'private' scope in the oauth_access_tokens table, but when both
tokens share the same value, only the public scope is registered.

Separate SERVICE_PASSWORD_LOGFLARE_PRIVATE secret ensures Logflare
generates distinct tokens with correct scopes on startup.
This commit is contained in:
Vadko 2026-03-09 02:32:28 +02:00
parent dd29e13573
commit a43e3b56e1
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
templates/compose/supabase.yaml
View file

@ -355,7 +355,7 @@ services:
- LOGFLARE_API_KEY=${SERVICE_PASSWORD_LOGFLARE}
- LOGFLARE_PUBLIC_ACCESS_TOKEN=${SERVICE_PASSWORD_LOGFLARE}
- LOGFLARE_PRIVATE_ACCESS_TOKEN=${SERVICE_PASSWORD_LOGFLARE}
- LOGFLARE_PRIVATE_ACCESS_TOKEN=${SERVICE_PASSWORD_LOGFLARE_PRIVATE}
- LOGFLARE_URL=http://supabase-analytics:4000
# Next.js client-side environment variables (required for browser access)
- 'NEXT_PUBLIC_SUPABASE_URL=${SERVICE_URL_SUPABASEKONG}'
@ -694,7 +694,7 @@ services:
- DB_PASSWORD=${SERVICE_PASSWORD_POSTGRES}
- DB_SCHEMA=_analytics
- LOGFLARE_PUBLIC_ACCESS_TOKEN=${SERVICE_PASSWORD_LOGFLARE}
- LOGFLARE_PRIVATE_ACCESS_TOKEN=${SERVICE_PASSWORD_LOGFLARE}
- LOGFLARE_PRIVATE_ACCESS_TOKEN=${SERVICE_PASSWORD_LOGFLARE_PRIVATE}
- LOGFLARE_SINGLE_TENANT=true
- LOGFLARE_SUPABASE_MODE=true