📎API Refactoring

[sugar-cat7]

Description

The current plan is to migrate all API and Cron handlers from the private repository to this repository, making the APIs more manageable and user-friendly.

now:

API
- CRUD operations for Channel information
- CRUD operations for Broadcasts, YoutubeClips, and TwitchClips
- CRUD operations for Event information

Cron
- Regular addition and updates of Channels, Broadcasts,  YoutubeClips, and TwitchClips
- Operation of Discord Bot

The new API will introduce the concept of Creator above the channel, making it easier to manage channels of each platform tied to a creator. Also, Integrate Broadcasts, YoutubeClips, and TwitchClips Model to Video Model.

Tasks

April: Cron (private repo -> common/cron Replace with Go)

Conveniently referred to as "distribution", but here it is unified as Video regardless of whether it is distribution or not, it is treated as Video whether it is distribution or clipping.

• [x] Automatic update of creator (Unified management of channel information, represented by Youtube Channel)
• [x] Automatic update of distribution information (Youtube)
• [ ] Automatic update of distribution information (Twitch)
• [ ] Automatic update of distribution information (Twitcasting)
• [ ] Automatic update of clips (Youtube)
• [ ] Automatic update of clips (Twitch)
• [ ] Segregation to different infrastructure

May: Discord Bot (Replace with Go + New feature development)

• [ ] Regular push of distribution information
• [ ] Save channel information / Review of authority
• [ ] Channel name change function

June: API (private Repo -> Implement in each service's directory e.g.) Define in API Route of schedule/web If there is something to be segregated into common parts, segregate it)

• [ ] Distribution information (CRUD)
• [ ] Clips (CRUD)
• [ ] Channel (CRUD)
• [ ] Frontend integration

[sugar-cat7]

~~I plan to get it to a stage where it can be verified by the end of next week. 🫠 If there are no issues with the updates after running it for a few days, I will gradually integrate it into the frontend.~~