Tableau de Bord
Supa Storage BU
Local Supabase Storage backup procedure. This backs up uploaded files/images from Supabase Storage only. It does not back up PostgreSQL database tables.
What this backup creates
A local timestamped folder containing downloaded Supabase Storage objects/files. For BrixFax, the important bucket is:
brixfax-public-images Step 1: Open normal CMD
Run this from the local backup workspace, not from the deployed web app.
cd /d C:\Sites\Codex Step 2: Create a timestamped Storage backup folder
Use a fresh folder name for each backup run.
mkdir supabase_storage_backup_YYYY_MM_DD_HH-mm
cd supabase_storage_backup_YYYY_MM_DD_HH-mm
mkdir storage Step 3: Login/link Supabase CLI if needed
If Supabase CLI is already logged in and linked, this may be fast or partly skipped. If it shows a verification code, complete the login locally in the browser/terminal flow.
npx supabase login
npx supabase init
npx supabase link If asked to choose a project, choose the BrixFax project.
Step 4: Copy the Storage bucket locally
npx supabase storage cp -r ss://brixfax-public-images .\storage --experimental --linked
Expected result: the bucket contents are downloaded under the local
storage folder.
Step 5: Check the output
Confirm that the backup folder contains a Storage folder with the downloaded
brixfax-public-images files inside it.
Important safety rules
- This page does not run the Storage backup.
- This page does not store Supabase tokens.
- This page does not store database passwords.
- Run the backup locally from CMD or PowerShell.
- Database backup is separate and is handled by the Supa DB BU page.