Self-hosting Supabase - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start the Supabase Docker container with the correct image tag.

Supabase

docker run -d --name supabase [1]

Drag options to blanks, or click blank then click option'

Asupabase/supabase:edge

Bsupabase/supabase:beta

Csupabase/supabase:stable

Dsupabase/supabase:latest

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'latest' tag which may not be stable

Using 'beta' tag which is for testing

Using 'stable' tag which is not a valid tag

The edge tag is used to run the latest build of Supabase for self-hosting.

2fill in blank

medium

Complete the command to expose Supabase's Postgres port correctly.

Supabase

docker run -d -p [1]:5432 supabase/supabase:edge

Drag options to blanks, or click blank then click option'

A5432

B5434

C5433

D5435

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different port number that is not mapped correctly

Not exposing the port at all

Port 5432 is the default Postgres port and should be exposed to the same port on the host.

3fill in blank

hard

Fix the error in the environment variable setting for the Supabase API key.

Supabase

docker run -d -e SUPABASE_API_KEY=[1] supabase/supabase:edge

Drag options to blanks, or click blank then click option'

Amyapikey

B"myapikey"

C'myapikey'

D${myapikey}

Attempts:

3 left

💡 Hint

Common Mistakes

Not quoting the API key causing shell errors

Using single quotes which may not be interpreted correctly

Environment variable values should be enclosed in double quotes to be interpreted correctly.

4fill in blank

hard

Fill both blanks to configure Supabase to use a custom Postgres data directory and port.

Supabase

docker run -d -v [1]:/var/lib/postgresql/data -p [2]:5432 supabase/supabase:edge

Drag options to blanks, or click blank then click option'

A/custom/pgdata

B5433

C5432

D/var/lib/postgres/data

Attempts:

3 left

💡 Hint

Common Mistakes

Using the container path instead of host path for volume

Using the default port 5432 when it may be in use

The volume mount uses the custom directory /custom/pgdata and the host port is set to 5433 to avoid conflicts.

5fill in blank

hard

Fill all three blanks to set environment variables for Supabase's JWT secret, API key, and database URL.

Supabase

docker run -d -e JWT_SECRET=[1] -e SUPABASE_API_KEY=[2] -e DATABASE_URL=[3] supabase/supabase:edge

Drag options to blanks, or click blank then click option'

A"supersecretjwt"

B"apikey123"

C"postgres://user:pass@localhost:5432/dbname"

Dsupersecretjwt

Attempts:

3 left

💡 Hint

Common Mistakes

Not quoting environment variable values

Using incorrect database URL format

All environment variable values should be enclosed in double quotes for proper parsing.

Practice

1. What is the main benefit of self-hosting Supabase compared to using the hosted service?

easy

A. It provides free hosting without limits.

B. It automatically scales without any setup.

C. You don't need to manage any servers or updates.

D. You get full control over your backend and data.

Solution

1. Step 1: Understand self-hosting meaning

   Self-hosting means you run the service on your own machine or server, giving you control.

2. Step 2: Compare benefits

   Unlike hosted services, self-hosting lets you manage data and backend fully, but requires maintenance.

3. Final Answer:

   You get full control over your backend and data. -> Option D

4. Quick Check:

   Self-hosting = full control [OK]

Hint: Self-hosting means you control your backend fully [OK]

Common Mistakes:

• Thinking self-hosting means no maintenance needed
• Assuming self-hosting is always free
• Confusing self-hosting with automatic scaling

2. Which command is used to start Supabase services using Docker Compose?

easy

A. supabase start

B. docker compose up -d

C. docker start supabase

D. docker run supabase

Solution

1. Step 1: Identify Docker Compose usage

   Supabase self-hosting uses Docker Compose to manage multiple services together.

2. Step 2: Recall correct Docker Compose command

   The command to start services in detached mode is docker compose up -d.

3. Final Answer:

   docker compose up -d -> Option B

4. Quick Check:

   Start services with docker compose up -d [OK]

Hint: Use 'docker compose up -d' to start all services [OK]

Common Mistakes:

• Using 'docker start' which starts single containers only
• Typing 'supabase start' which is not a Docker command
• Using 'docker run' which runs a new container, not compose

3. Given this Docker Compose snippet for Supabase services:

services:
  db:
    image: supabase/postgres:latest
  api:
    image: supabase/api:latest
    depends_on:
      - db

What happens if you run docker compose up?

medium

A. Both db and api services start, with api waiting for db.

B. Only db service starts, api is ignored.

C. api starts before db, causing errors.

D. No services start due to missing volumes.

Solution

1. Step 1: Understand depends_on behavior

   The depends_on means api waits for db container to start before launching.

2. Step 2: Analyze docker compose up effect

   Running docker compose up starts all defined services; api waits for db as specified.

3. Final Answer:

   Both db and api services start, with api waiting for db. -> Option A

4. Quick Check:

   depends_on makes api wait for db [OK]

Hint: depends_on ensures service start order in Docker Compose [OK]

Common Mistakes:

• Thinking depends_on delays start until db is ready (it waits only for start)
• Assuming api won't start without volumes (not required here)
• Believing only one service starts by default

4. You tried to start Supabase with Docker Compose but get a database connection error. Which fix is most likely correct?

medium

A. Change the Supabase API image to an older version.

B. Remove the Docker Compose file and reinstall Docker.

C. Check if the database service is running and accessible.

D. Disable the firewall on your local machine.

Solution

1. Step 1: Identify cause of connection error

   Database connection errors usually mean the database service is down or unreachable.

2. Step 2: Verify database service status

   Check if the database container is running and network settings allow access.

3. Final Answer:

   Check if the database service is running and accessible. -> Option C

4. Quick Check:

   Database connection error = check DB service [OK]

Hint: Verify database container is running first [OK]

Common Mistakes:

• Assuming reinstalling Docker fixes connection errors
• Changing API image without checking DB status
• Disabling firewall without confirming network issues

5. You want to secure your self-hosted Supabase database. Which practice is best to protect your data?

hard

A. Use strong passwords, restrict network access, and enable SSL connections.

B. Run the database on default ports and allow all IPs.

C. Disable authentication to simplify access for developers.

D. Store database backups on the same server without encryption.

Solution

1. Step 1: Identify security best practices

   Strong passwords, network restrictions, and SSL protect data from unauthorized access.

2. Step 2: Evaluate other options

   Default ports and open IPs increase risk; disabling auth or unencrypted backups are unsafe.

3. Final Answer:

   Use strong passwords, restrict network access, and enable SSL connections. -> Option A

4. Quick Check:

   Secure DB = strong passwords + network + SSL [OK]

Hint: Secure DB with passwords, network limits, and SSL [OK]

Common Mistakes:

• Leaving default ports open to the internet
• Disabling authentication for convenience
• Not encrypting backups or storing them insecurely