Site providing information on MMA athletes
Player search screen
Full execution screen
It was the first project created simply with React around March 2021, and it was a more meaningful development than I thought. This is not only because it is the first toy project, but even more so because it is a result that is actually used consistently. There are few sites where you can view the records of martial arts players, and even those sites are thought to be inconvenient in accessibility, so I created this site, but it is often used by friends who like martial arts sports.
So, instead of neglecting the site, we are trying to fix it as much as possible whenever a problem arises. At first, it did not support responsive design, but it was developed as responsive, and whenever there is a problem with the server, we try to fix the error as much as possible.
At first, I thought I really wanted to make something with this idea rather than the technology, so I started developing it, but when I thought about it, I was disappointed in the technical aspect because it was an app that only had to fetch data from the server and distribute it.
As these regrets piled up, I later developed the todo app with a front (react) and back (express) full stack. In the toy project that I continued to work on, I was disappointed that I had to learn while working on the project, and I wanted to learn the back-end as well, so I decided to do it.
There was an open source mma-api that I originally planned to use, but it didn't work, so I forked it and did a little tweaking. However, as I crawled from the bag and sent the data, sherdog's form changed, so I had to write the API again.
Recently (around June 2022), I heard that the site was not working. When I checked, it turned out that the site was not working because googleIt was not crawling properly. Obviously, since data is collected from the server and sent through crawling, it does not seem to be stable.
There were many trials and errors while distributing the front end through Github Pages and distributing data from the back end with a personal domain called https://server.woog2roid.dev. Starting with how to deploy the backend, I started by running a node on a free cloud server, but I was concerned that it was inconvenient to use because the server did not have an https connection, so I ended up purchasing a private domain and using let's encrypt to connect to https. was supported.