Todo is a modern, user-friendly task management app designed to help users efficiently organize their daily activities. With a clean and intuitive interface, Todo allows users to create, manage, and track tasks effortlessly. With core features such as user authentication, task management, real-time updates, data synchronization, and notifications, Todo targets anyone looking to streamline their daily tasks, from professionals managing work projects to students organizing their study schedules.
Our website was built, compiled and then hosted on netlify. 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 your browser.
The page will reload when you make changes.
You may 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
- Load Balancer
We used HAProxy as the load balancer in this project. It was set up to serve requests to 2 servers using round-robin load balancing algorithm. Since only one server has MYSQL set up as the master in the replication, all requests that manipulate data are sent to server1.
- Webserver
We used NGINX to serve and respond to HTTP requests to/from clients. The webservers were set up to allow only a few headers, and handle preflight requests.
The webservers host static files such as html, css, and javascript files built using React. It also redirects all requests to the uri /api/v1 to the virtual application server using gunicorn service running on port 5000 on the server.
- Application server
We used a gunicorn, a python WSGI HTTP server for UNIX. It was set up to run as a service listening on port 5000 on each server. It binds requests made to port 5000 to the flask application which incudes all the api endpoints. The flask application fetches data from the MYSQL database using mysqldb, and sqlalchemy.
NOTE: All endpoints except /status, /stats, and /users/register require the Authorization header with a Bearer Token for authentication.
-
GET /status
Checks if the server can respond to requests -
GET /stats
Returns the count of all models stored in the database -
GET /tasks
Returns all tasks of that user. This endpoint allows filtering params i.e?status=Pending,?sort,?limit=3,order=asc|desc -
POST /tasks
Creates a task under that user -
PUT /tasks/<task_id>
Updates the task with the task_id based on the sent data. -
POST /tasks/search
Returns results based on the sent filter data. The sent data should be in the form below;{ "filters": { "condition": "OR | AND", # specifies how rules shall be matched "rules": [ { "field": '<column>', # column to search "operator": 'eq|neq|like', # condition to match the value "value": '<value>' # value to match }, ] } } -
DELETE /tasks/<task_id>
Deletes the task with the provided task_id -
POST /users/register
Creates a new user -
GET /users_profile
Returns the data of the currently logged in user -
PUT /update_user
Updates data of the current user based on the data sent
-
First clone this repository.
-
Access the Todo App directory
-
Once the repository is cloned locate the "console.py" file and run it as follows:
/AirBnB_clone$ ./console.py
-
When this command is run the following prompt should appear:
(todo)
-
This prompt designates you are in the "Todo" console. There are a variety of commands available within the console program.
-
destroy - Destroys an object based on class and UUID
-
show - Shows an object based on class and UUID
-
all - Shows all objects the program has access to, or all objects of a given class
-
update - Updates existing attributes an object based on class name and UUID
-
quit - Exits the program (EOF will as well)
Signup or login with Google, create, edit, delete or mark a task as complemted, and get notified when a task delays.
GNU General Public License (GPLv3)