A proof of concept demo for a Game of the Month Discord bot, intended to host a chat where users can nominate games, create preview images using the nominations, run a vote using these preview images, and display the final result.
This demo focuses on the building of preview images using information scraped with the ScreenScraper API. The user can type the name of a "nominated" game into the textbox. Upon submission, the demo will scrape information for the game and build up a preview image, using ScreenScraper data, with each nomination.
- Clone the repo to a local project directory.
git clone https://github.com/ryandavidmercado/gotm-test - Copy the sample environment file to .env.
cp .env.sample .env - Supply the environment file with your ScreenScraper dev_id and dev_password.
nano .env...
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.