This project is a proof of concept for learning React. It reproduces a master/detail presentation by using movies' data from The Movie Database - TMDb (https://www.themoviedb.org)
Firebase is used as hosting service and the app is automatically deployed when GitHub actions are trigerred (see folder .github/workflows).
-
On push actions, the project is build
-
On pull actions, the project is deployed to a test environment.
-
On merge to
master
actions, the project is deployed in the production environment:
On all actions, the tests are executed (npm test).
If you'd like to test this project on your machine, you'll need to:
-
execute
npm ci
after cloning the project -
create an account on https://www.themoviedb.org and get your API key
-
create a file named
tmdb.json
in folderservices
having the following structure and replaceYOUR_KEY
with your API key:{ "key": "YOUR_KEY" }
-
execute
npm start
If you'd like to have your own environments, you'll need to:
- create 2 new projects on Firebase: 1 for TEST and 1 for PROD
- use the firebase-cli command to add the deployment token to your GitHub secrets in your project
- add a GitHub secret named
TMDB
containing the token from The Movie Database to your project - replace the value
FIREBASE_SERVICE_ACCOUNT_MOVIEPOLIS_TEST
in the file.github/workflows/firebase-hosting-pull-request.yml
by the keyname generated by the firebase-cli command for your TEST project - replace the value
FIREBASE_SERVICE_ACCOUNT_MOVIEPOLIS_647C7
in the file.github/workflows/firebase-hosting-merge.yml
by the keyname generated by the firebase-cli command for your PROD project
This project was bootstrapped with Create React App.
In the project directory, you can run:
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.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.