Please follow these steps to run this application on your local machine:
-
visit https://openweathermap.org/appid and sign up to receive an API key (APPID)
-
you will receive a welcome email with detailed instructions on api key usage (check junk mail also)
-
NOTE: It can take up to a few hours for the api key to get activated. You will NOT be able to run this application successfully until that happens (you will keep getting 401 unauthorized errors)
-
clone this repo into a folder in your local machine (detailed instructions available at https://www.git-tower.com/learn/git/commands/git-clone)
-
navigate into application folder (cd cbc-web-presentation)
-
run npm install
-
create a new file in the project root folder (cbc-web-presentation) called '.env'
-
Paste the following line into the newly created .env file: REACT_APP_WEATHER_API_KEY = YOUR_API_KEY
-
Note that in the line above, 'YOUR_API_KEY' will be replaced by the api key you receive from open weather map on registration. The api key MUST be active and should NOT be in quotes; you will paste it as is
-
save the .env file
-
run npm start
-
The last command (npm start) should automatically open http://localhost:3000/ in a browser. If it doesn't, simply navigate to http://localhost:3000/ in a browser
-
Last, but not the least, Enjoy the app!
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.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify