Han Qiao

Thanks for checking. Our current recommendation is to always use schema qualified references in your migration file. For eg. ```sql CREATE TABLE test (path extensions.ltree NOT NULL); ``` This avoids...

> improve the error message when an extension type isn’t found > optionally add a CLI hint suggesting extensions.ltree Do you plan to do this by inspecting the error object...

Deploying static files in non-docker mode is supported. Can you reproduce the issue and verify?

> With --use-docker and Docker stopped: deploy succeeds but static files are missing This code path falls back to deploy using API, which is the same as running `supabase functions...

The docs for this command lives here https://github.com/supabase/cli/blob/develop/docs/supabase/db/pull.md if you want to update it. It will be published to main supabase repo on next stable release (in 2 weeks time)....

Which container do you think is unused? The database depends on service migrations from auth, storage, and realtime. So running `supabase db start` alone will require pulling 3 additional service...

To close this one off, you can now selectively disable services in `supabase/config.toml` to skip initialising those schemas on supabase start. This also means that images for disabled services won't...

> It would be more flexible and intuitive to prevent container downloads (in addition to not running them) when the exclude flag is provided to supabase start. I think that's...

The only way to exclude storage and realtime images from downloading is to disable those services in config.toml. ``` [storage] enabled = false [realtime] enabled = false ```

The auth, storage, and realtime images are special because they contain schema migrations to initialize the database. If you exclude any of them via `-x` flag, those containers will not...