Update telescope_profiles and feeds tables

[DukeManh]

Issue This PR Addresses

Part of #2860

This updates feeds table schema in preparation for migrating Planet feed list to Supabase.

Schema

Field	Description
url	text - primary key - unique feed url
user_id	text - optional foreign key - A register can claim an existing feed when they register for Telescope
author_name	text - author name get from Planet, will be unused when the feed is linked with a user
html_url	text optional - Actually blog URL of the RSS feed
type	'blog' | 'youtube' | 'twitch'
flagged	boolean
Invalid	boolean

Steps to test the PR

1. Pick up the new schema script

    docker-compose stop db && docker-compose rm db
    docker-compose up db -d
   

2. Rebuild the SSO service

    docker-compose build sso
   

3. Start all services

    pnpm  dev
    pnpm services:start
   

4. Register Telescope user at http://localhost:8000/signup
5. If a feed entered is already associated with a user, registration should fail

[gitpod-io]

[DukeManh]

@tcvan0707 This made a slight change to how a feed is considered to be invalid. A user can add an existing feed if it is not already linked with a Telescope user, or the user_id is null.

[DukeManh]

@humphd and @JerryHue, I might miss some properties as suggested here #2860 (comment), let me know.

[TueeNguyen]

@JerryHue said to change link to source or src_link. I don't think link is descriptive enough but for me it's fine

[humphd]

html_url is probably better than link, such that url is a feed URL, and html_url is for HTML.

[DukeManh]

html_url is probably better than link, such that url is a feed URL, and html_url is for HTML.

I changed link -> html_url

[cindyledev]

I noticed you initially created the telescope_profiles table without explicitly passing a schema which means Postgres creates the table in the public schema. Would this be a problem in the future?

From Supabase Tables docs

Tables belong to schemas. If you don't explicitly pass the schema, Postgres will assume that you want to create the table in the public schema.

[DukeManh]

@cindyledev, we want to put them public schema so they are exposed to the client.
When you write supabase.from('telescope_profiles').select('*'), supabase is going to look for the table in the public schema. There shouldn't be a problem if we have RLS to give/deny access to certain users.

[humphd]

Looks good, a few small things.

[Kevan-Y]

@DukeManh followed the steps. I'm getting this 🔽


I have the user stored in the database, but not for the feed.

[DukeManh]

You'll need to run the frontend server with pnpm run dev, I've updated the instructions. Can you try again?

[humphd]

Good point, I'm wrong about html url from wiki. Looks good

[DukeManh]

Thank you, everyone.