What is the primary purpose of running supabase init in a new project directory?
Think about what happens locally when you start using Supabase CLI in a folder.
The supabase init command sets up local files and folders that the CLI uses to manage your project. It does not create cloud projects or deploy schemas.
Which command correctly logs you into your Supabase account using the CLI?
Check the official Supabase CLI command for authentication.
The command supabase login opens a browser window to authenticate your account with the CLI.
After running supabase init, which folder does the CLI create to store your local database migrations and seed files?
Look for the folder inside the supabase directory that holds migration files.
The CLI creates a supabase/migrations folder to keep track of database schema changes locally.
Where does the Supabase CLI store your access token after login, and what is the best practice for securing it?
Think about how CLI tools usually store sensitive tokens securely on your computer.
The Supabase CLI stores tokens securely in the OS keychain or credential store to protect them from unauthorized access.
What happens if you run supabase start on a machine where Docker is not installed or running?
Consider what the Supabase CLI depends on to run local services.
Supabase CLI requires Docker to run local services. Without Docker, it cannot start and will show an error.