You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
After update to 1.203.3 containers won't start due to missing FILE_STORAGE_BACKEND_PATH env variable #2738
Describe the bug
After update to 1.203.3 containers won't start due to missing FILE_STORAGE_BACKEND_PATH env variable
To Reproduce
Steps to reproduce the behavior:
Update from an earlier version to 1.203.3 (I updated from 1.200.3)
Expected behavior
Updates to supabase cli should always automatically make any required configuration changes and/or inform the user of changes that need to be made.
Screenshots
n/a
System information
Rerun the failing command with --create-ticket flag.
/app/dist/storage/backend/file.js:64
throw new Error("FILE_STORAGE_BACKEND_PATH env variable not set");
^
Error: FILE_STORAGE_BACKEND_PATH env variable not set
at new FileBackend (/app/dist/storage/backend/file.js:64:13)
at createStorageBackend (/app/dist/storage/backend/index.js:35:22)
at Object.<anonymous> (/app/dist/storage/events/base-event.js:36:64)
at Module._compile (node:internal/modules/cjs/loader:1469:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1548:10)
at Module.load (node:internal/modules/cjs/loader:1288:32)
at Module._load (node:internal/modules/cjs/loader:1104:12)
at Module.require (node:internal/modules/cjs/loader:1311:19)
at require (node:internal/modules/helpers:179:18)
at Object.<anonymous> (/app/dist/storage/events/webhook.js:34:25)
I see there is a variable for storage config STORAGE_FILE_BACKEND_PATH as opposed to FILE_STORAGE_BACKEND_PATH -- is this possibly just a typo bug in supabase-cli?
Activity
sos0 commentedon Oct 9, 2024
This happens prior to update as well, on 1.19x