Self host Supabase service

[DukeManh]

Issue This PR Addresses

Part of #2555. This adds a Supbase self-hosted instance to Telescope.

Note: This pr also fixes the SignUpPage crash bug mentioned in #2676. @nguyenhung15913 , you can take a look at AuthProvider here as a starting point of your PR.

Type of Change

• Bugfix: Change which fixes an issue
• New Feature: Change which adds functionality
• Documentation Update: Change which improves documentation
• UI: Change which improves UI

Description

Testing Supabase

1. Go to the Supabase service

  cd src/api/supabase

2. Copy the env vars

  cp .env.example .env

3. Start

  docker-compose up

4. Go to localhost:8910 to visit the Dashboard

Testing Supabase API in the auth service

1. Do all the steps above
2. Uncomment Sign Up link in BannerButtons in

   telescope/src/web/src/components/BannerButtons.tsx

   Lines 111 to 120 in 81775c4

   	{/* <Link href="/signup" passHref>
   	<Button
   	style={{
   	fontSize: '1.3rem',
   	}}
   	variant="outlined"
   	>
   	Sign up
   	</Button>
   	</Link> */}

3. In /src/api/auth/src/middleware.js, replace line 92 to 110
   

   telescope/src/api/auth/src/middleware.js

   Lines 92 to 110 in 81775c4

   	const id = getUserId(req);
   	const response = await fetch(`${USERS_URL}/${id}`, {
   	method: 'POST',
   	headers: {
   	// re-use the user's authorization header and token
   	Authorization: req.get('Authorization'),
   	'Content-Type': 'application/json',
   	},
   	body: JSON.stringify(req.body),
   	});
   	if (response.status !== 201) {
   	logger.warn(
   	{ status: response.status, id, data: req.body },
   	'unable to create user with Users service'
   	);
   	next(createError(response.status, 'unable to create user'));
   	return;
   	}

with

      const supabase = require('./supabase');
      ...
      const { email } = req.user;
      const { user, error } = await supabase.auth.api.createUser({
        email,
        password: 'hello',
        data: req.body,
      });

      if (error) {
        logger.warn({ status: error.status, email, data: req.body }, error.message);
        next(createError(error.status, 'unable to create user'));
        return;
      }

4. Go to localhost:8000 to Sign Up using an example account:
   • username: user1
   • password: user1pass
5. Finish the user registration flow
6. Vist the Supabase dashboard again at localhost:8910 and check the user list. A new user is created!

Checklist

• Quality: This PR builds and passes our npm test and works locally
• Tests: This PR includes thorough tests or an explanation of why it does not
• Screenshots: This PR includes screenshots or GIFs of the changes made or an explanation of why it does not (if applicable)
• Documentation: This PR includes updated/added documentation to user exposed functionality or configuration variables are added/changed or an explanation of why it does not(if applicable)

[gitpod-io]

[humphd]

Filed #2748 to fix the auth build

[DukeManh]

Why do I have pnpm-lock.yaml after installing @supabase/supabase-js? I installed with pnpm add inside 'sr/api/auth'

[humphd]

Created #2752 to fix the naming of auth containers.

[humphd]

Can you rebase to pick up the changes from #2752?

[humphd]

Let's move supabase out of src/api and put it in docker/supabase, since that's what it is (i.e., a bunch of docker and config files).

Next, let's modify https://github.com/Seneca-CDOT/telescope/blob/master/config/env.development#L13 so that it adds a third docker-compose file to our list:

COMPOSE_FILE=docker/docker-compose.yml;docker/development.yml;docker/supabase/docker-compose.yml

Next, let's move everything in supabase/env.example to config/env.development under a new Supabase section. That is, let's merge the Supabase variables with ours.

Next, lets update all of the volumes relative paths in the Supabase docker-compose files (there are two), so that it uses ./supabase/volumes vs. ./volumes. We'll have to confirm that I have this right, but basically, we need to use a relative path for the new location, which is the merged path (i.e., the first docker-compose.yml we have in docker).

We won't add any of this to staging or production yet, only for development and gitpod. That way we can iterate on it and secure things before we ship it to staging.

[DukeManh]

@humphd works for me on Gitpod.

[DukeManh]

@manekenpix, could you also take a look, please?

[manekenpix]

Keeping an eye on the open ports