A full-stack web application that delivers the best basketball highlight experience you can receive. Curated videos, filtered, sorted, and save any of your favorites as well. This repo contains the server side of the application while the client side can be seen here.
- Portfolio
- GitHub: Alex-Lee-Myers
- Email: [email protected]
- Twitter: @AlexLeeMe
Click me to view the live deploy through Heroku.
Click me to view the Client repo for AllBallCall.
P.E.R.N. (PostgreSQL, Express, React, Node.js)
Due to the nature of this project being required to reach MVP within 25 days, from server to client side, a host of packages were implemented to quicken progress on the server side.
- BcrpytJS
- Express
- .env
- JsonWebToken
- PostgreSQL
- Sequelize
- UUID
Well, I did! I have over half a decade of experience in Illustrator and spent around 30 minutes on producing it.
I am a die-hard NBA fan. In the midst of working a full-time job as well as averaging 5 hours a night coding for my part-time bootcamp with Eleven Fifty Academy, I was unable to watch any games or keep up. I started to rely on Twitter or Reddit.com/r/NBA for highlights yet both were cumbersome to do so. I wanted a one-stop shop where I could find the highlights I wanted to see --- so I decided to make it myself.
Yes! Soon enough I will provide an experience beyond the scope of my intensive class. I may make it open-source in the future as well as I'd love to work with the community to build the best experience for all.
Indeed I am. Feel free to reach out to me via my LinkedIn if you have positions available for front-end, back-end, and/or full-stack.
- Week 1 (January 22nd through January 29th, 2022)
- Completed MVP of Server.
- Build out base structure of Client MVP.
- Test client-side register and login.
- Start implementing ReactPlayer and testing its functionality to ready for server fetch.
- Week 2 (January 30th through February 5th, 2022)
- Setup possible Admin functionality that was later deprecated.
- Changed endpoints to reflect initial planning document.
- Week 3 (February 5th through February 12th, 2022)
- Admin functionality was now working.
- Users are able to edit their username, password, and email.
- Cleaned up route names to reflect front-end as well.
- Week 4 (February 12th through February 19th, 2022)
- Head to San Diego...🌞⛱
- Heroku deployed.
- Fixed CORS issue with pre-flights not accepting.
- Comments controller changed to be able to edit comments.
- User controller changed slightly to allow admin functionality.
- Week 5 (February 19th through February 24th, 2022)
- Ensured as much as possible it was working for presentation on Feb 22.
- Presentation Day: Ran into first-time issues during the presentation with CORS.
- Tuesday, February 22: Presentation Day
- Potentially fixed most, if not all, CORS issues on Heroku side the day after presentation.
- Continued Support (March 2022 and beyond)
- No current future plans on server side. Will update as needed.
| Date | Comments |
|---|---|
| 1/22/22 | Started my server build. Ran into extreme issues with PostgreSQL on my host computer that set me back a few hours. I ended up having to manually seek out all PostgreSQL related files within /AppData, /ProgramFiles, etc., delete them, then reinstall PostgreSQL from scratch. |
| 1/23/22 | After snafu of previous day, spent nearly 10 hours on development of my server mostly betweem researching database associations, applying them, and continuing to narrow down the tables I'd need for MVP. |
| 1/24/22 P.1 | Trello Board created. |
| 1/24/22 P.2 | Continued finalizing database associations. Ran into issues with primary keys conflicting with foreign keys. Setup some potential stretch goal tables/models regarding bookmarks and upvote features. |
| 1/25/22 | Debugged my issues with table's being set incorrectly and now fully functional, tested all endpoints as well. |
| 1/26/22 | Finished up UI design of the NavBar. Built out extremely limited React-Router-Dom. Debugged issues ts-node was flagging regarding it. Still need to figure out drop-down of the Portfolio and create terenary depending on isLoggedIn state for Logout+Signin/Register. |
| 1/27/22 P.1 | Tested ReactPlayer functionality. Minimal Tailwind UI integration with a card-style grid. Base structure working. Need to move to Home.tsx and then integrate fetching the server. |
| 1/27/22 P.2 | Started build up of Login UI. Needs a lot more work before functional. Additionally, did a copy-paste into Register file for a base start. Will touch that after Login finished. |
| 1/28/22 | Working on Login+Register further and testing. Navbar dropdown as well. |
| 2/2/22 | UserModel prepped with Admin functionality. Later deprecated. |
| 2/5/22 | updated videopost and user models+controllers respectively to reflect changes in client. Admin registeration and login now functional. |
| 2/6/22 | updated usercontroller further to reflect the users ability to edit their account details between username, email, and password. |
| 2/10/22 | fixed up route names to adjust to client side naming conventions. |
| 2/12/22 | Heroku deployed on this day. Was running into CORS errors. They were all fixed by adding pre-flight acceptance from the cors npm package. |
| 2/13/22 | Database Associations already were set in index on MVP, the controllers are now addressing those associations. |
| 2/14/22 | Adjusted comments controller further for client-side flexibility. |
| 2/15/22 | updated comments controller to be more simplified for editing comments. commented out any further implementation. |
| 2/16/22 | updated comment controller for front end variation. |
| 2/20/22 | updated for admin use cases on client side. |
| 2/23/22 | Heroku client was running into CORS issues right in the middle of my presentation last night. For reference, it was the first time I ran into any CORS issues, and it happened to be in the middle of my presentation. Oh well! Demo day trials are like that sometimes. Ran multiple attempted fixes through Heroku and eventually found a fix with the use of whitelisting the client. It is now working on live Heroku build! Although, it seems on Logout() that a CORS error arises, but after refreshing it works again. |