Skip to content

Add Objectives for the second round of the Project HarmonyHub #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
novak-the-slovak wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add Objectives for the second round of the Project HarmonyHub #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 9 additions & 9 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,14 +8,15 @@

### Things to add

Class Diagrams for the backend models <br>
Session Management Diagram for HH <br>
Sample .env file <br>
1. Sample .env file <br>
2. Setup separate enviroments for prod and dev<br>
3. New Yahoo Email with name HarmonyHub<br>
4. Spotify Accounts should be unique for all users <br>
5. Implement Redis Based Caching to store user's spotify data for next 24 hours. Try utilising the CachingDecorator to achieve this. <br>
6. Provide Spotify-Sign-Up option, along with the currently present email-pass registeration. <br>

### Things to do before deployment

Setup separate enviroments for prod and dev<br>
New Yahoo Email with name HarmonyHub<br>
-> Class Diagrams for the backend models <br>
-> Session Management Diagram for HH <br>

### Plans

Expand All @@ -24,9 +25,8 @@ Use decorator pattern to support different caching mechanisms
Google Gemini para generate making fun of user's music taste <br>
Think about followers and following and how it's going to be implemented <br>
Think about how will the feed of common artist be generated <br>
Spotify Accounts should be unique for all users <br>

### Further Explorations and Improvements

Think about implementing an external rate limiter wherever required. Currently rate limiting email requests sent within five minutes, move this functionality to external limiter. <br>
Allow user to send more than one emails for activation link or password reset within the specified duration <br>
Allow user to send more than one emails for activation link or password reset within the specified duration <br>