Skip to content

Latest commit

 

History

History
108 lines (66 loc) · 3.65 KB

README.md

File metadata and controls

108 lines (66 loc) · 3.65 KB

Hackers In Residence

I am developing this automation app solution to help mitigate and/or create an organized schema/way of how hackers and residents of the Nkwashi smart city live their day to day life, through automation of everyday life activities.

  • Its basically a side project automation solution to common problems I observe on a daily basis while living in Nkwashi under the Microverse program

Please, see the video explaining some core functionality of the app


Built With

  • JavaScript
  • React JS
  • Redux
  • HTML & CSS of course :-)

Deployed On

GitHub Pages

Getting Started

To get a local copy up and running follow these simple example steps.

Prerequisites

  • some knowledge on npm , webpack, JavaScript(ES6) and React
  • Node.js
  • Web browser
  • Code Editor

Setup

  • Clone repository using this command in terminal git clone https://github.com/blessedjasonmwanza/hackers-in-residence.git
  • Change directory to the cloned repository cd hackers-in-residence
  • Install dependencies using npm install
  • run npm start

Available Scripts

In the project directory, you can run:

npm start

Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.

The page will reload when you make changes.
You may also see any lint errors in the console.

npm test

Launches the test runner in the interactive watch mode.\

npm run build

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!

npm run eject

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.

Authors

👤 Blessed Jason Mwanza

🤝 Contributing

Contributions, issues, and feature requests are welcome!

Feel free to check the issues page.

Show your support

Give a ⭐️ if you like this project!

📝 License

This project is MIT licensed.

The Idea is from my mind but - images and branding used belong to their respect owners. (Don't come suing me :-) )