themisbahnator/reverbify-api

API that automates audio processing by adding Daycore/Nightcore twist to your favorite songs

reverbify-api's Issues

Set up AWS S3

• Turn off the S3 bucket for the last project and create a new one
• When downloading the mp3 file, store in the S3 Bucket
• Figure out a proper naming convetion (might rely on MongoDB to create unique keys)

Set up MongoDB (w schema)

• Create the collection document schema outlined below
• figure out how to create the entities above using golang, and how to continue to populate the table as users request downloads
• here is a scheme brain plan below
  schema

file naming convention

change file naming convention so it isnt reliant on the title of the video but rather the user name, timestamp, and the effects placed on the video

Endpoints

Create some new endpoints

createUser - builds a folder within the s3 bucket for each user, figure out a way to make the name unique given the username
this should involve some authentication, maybe later you could implement this where you would also require the password when
making the request

getSong - given a username, we can access the specific folder in the s3 bucket and pull the requested file of the song
The other details like song link, title, and thumbnail will be stored in firebase, we could retrieve that here or get it on the mobile app
for credit

EXTRA: websocket connection that allows you to retrieve from edits made live through a socket connection sending messages back and forth.

Deployment

figure out a way to deploy the backend probably with netlify, aws or gcp. make sure its cheap cuz i aint that rich

Duration wrong

duration gives the time of the song before download, we need it after

Youtube link structure

Some videos from youtube cannot be downloaded for some reason. For example, music found in playlist have a different url structure from the same video not in the play list. Here is an example,

Creepin in a playlist: https://www.youtube.com/watch?v=LOqGYF0oFIg&list=RDoKtdps9Lm7A&index=2
Creepin on its own: https://www.youtube.com/watch?v=LOqGYF0oFIg

Figure out a way to reduce the first link into the second.

Progress bar

instead of a post request, figure out how to use websockets in golang to update the client after every step of the download and audio proccessing is complete. This will create more transparency on the front end.

youtube url

input validation is incorrect as it leads to a 500 error, fix that

title in response

title in response gets cut off by one character

Sign/log in functionality

• create sign in functionality where users can create accounts
• figure how to use bcrypt to encrypt passwords so they are safe to store
• enpoints probably need
  • create account
  • change password
  • signing in (returning some token to use the rest of the api services)
• connect with mongoDB

youtube-dl

replace all instances of youtube-dl in place of ytdlp or another method to replace the way to get titles of youtube videos.

Docker

Create a docker container that runs the application locally (at first)

• should have the exectubles ffmpeg, ytdlp, and youtube-dl within the container
• should also have a build directory that clones this projects and runs it