Welcome to DocuThinker! This is a full-stack (FERN-Stack) application that integrates an AI-powered document processing backend with a React-based frontend. The app allows users to upload documents for summarization, generate key insights, and chat with an AI based on the documentβs content.
The DocuThinker app is designed to provide users with a simple, AI-powered document management tool. Users can upload PDFs or Word documents and receive summaries, key insights, and discussion points. Additionally, users can chat with an AI using the documentβs content for further clarification.
DocuThinker is created using the FERN-Stack architecture, which stands for Firebase, Express, React, and Node.js. The backend is built with Node.js and Express, integrating Firebase for user authentication and MongoDB for data storage. The frontend is built with React and Material-UI, providing a responsive and user-friendly interface.
It is currently deployed live on Vercel and Render. You can access the live app here.
We have deployed the entire app on Vercel and Render. You can access the live app here.
Note: The backend server may take a few seconds to wake up if it has been inactive for a while. The first API call may take a bit longer to respond. Subsequent calls should be faster as the server warms up.
Additionally, the app is currently on the Free Tier of Render, so it may take longer to process your request since we are only allocated 512MB and 0.1 CPU.
DocuThinker offers a wide range of features to help users manage and analyze their documents effectively. Here are some of the key features of the app:
DocuThinker features a clean and intuitive user interface designed to provide a seamless experience for users. The app supports both light and dark themes, responsive design, and easy navigation. Here are some screenshots of the app:
The DocuThinker app is organized into separate subdirectories for the frontend, backend, and mobile app. Each directory contains the necessary files and folders for the respective components of the app. Here is the complete file structure of the app:
DocuThinker-AI-App/
βββ backend/
β βββ ai_ml/
β β βββ perform_ner_pos.py # Named Entity Recognition and Part-of-Speech Tagging
β β βββ sen_analysis.py # Sentiment analysis for document text
β β βββ chat.js # Chatbot integration for AI chat functionality
β β βββ analyzer.js # Document analyzer for generating key ideas and discussion points
β β βββ textStatistics.js # Text statistics for analyzing document content
β β βββ documentClassifier.js # Document classifier for categorizing documents
β β βββ summarizer.js # Document summarizer for generating summaries
β β βββ (and many more files...) # Additional AI/ML services
β βββ middleware/
β β βββ jwt.js # Authentication middleware with JWT for the app's backend
β βββ controllers/
β β βββ controllers.js # Controls the flow of data and logic
β βββ graphql/
β β βββ resolvers.js # Resolvers for querying data from the database
β β βββ schema.js # GraphQL schema for querying data from the database
β βββ models/
β β βββ models.js # Data models for interacting with the database
β βββ services/
β β βββ services.js # Models for interacting with database and AI/ML services
β βββ views/
β β βββ views.js # Output formatting for success and error responses
β βββ redis/
β β βββ redisClient.js # Redis client for caching data in-memory
β βββ swagger/
β β βββ swagger.js # Swagger documentation for API endpoints
β βββ .env # Environment variables (git-ignored)
β βββ firebase-admin-sdk.json # Firebase Admin SDK credentials (git-ignored)
β βββ index.js # Main entry point for the server
β βββ Dockerfile # Docker configuration file
β βββ manage_server.sh # Shell script to manage and start the backend server
β βββ README.md # Backend README file
β
βββ frontend/
β βββ public/
β β βββ index.html # Main HTML template
β β βββ manifest.json # Manifest for PWA settings
β βββ src/
β β βββ assets/ # Static assets like images and fonts
β β β βββ logo.png # App logo or images
β β βββ components/
β β β βββ ChatModal.js # Chat modal component
β β β βββ Spinner.js # Loading spinner component
β β β βββ UploadModal.js # Document upload modal component
β β β βββ Navbar.js # Navigation bar component
β β β βββ Footer.js # Footer component
β β β βββ GoogleAnalytics.js # Google Analytics integration component
β β βββ pages/
β β β βββ Home.js # Home page where documents are uploaded
β β β βββ LandingPage.js # Welcome and information page
β β β βββ Login.js # Login page
β β β βββ Register.js # Registration page
β β β βββ ForgotPassword.js # Forgot password page
β β β βββ HowToUse.js # Page explaining how to use the app
β β βββ App.js # Main App component
β β βββ index.js # Entry point for the React app
β β βββ App.css # Global CSS 1
β β βββ index.css # Global CSS 2
β β βββ reportWebVitals.js # Web Vitals reporting
β β βββ styles.css # Custom styles for different components
β β βββ config.js # Configuration file for environment variables
β βββ .env # Environment variables file (e.g., REACT_APP_BACKEND_URL)
β βββ package.json # Project dependencies and scripts
β βββ craco.config.js # Craco configuration file
β βββ Dockerfile # Docker configuration file
β βββ manage_frontend.sh # Shell script for managing and starting the frontend
β βββ README.md # Frontend README file
β βββ package.lock # Lock file for dependencies
β
βββ mobile-app/ # Mobile app directory
β βββ app/ # React Native app directory
β βββ .env # Environment variables file for the mobile app
β βββ app.json # Expo configuration file
β βββ components/ # Reusable components for the mobile app
β βββ assets/ # Static assets for the mobile app
β βββ constants/ # Constants for the mobile app
β βββ hooks/ # Custom hooks for the mobile app
β βββ scripts/ # Scripts for the mobile app
β βββ babel.config.js # Babel configuration file
β βββ package.json # Project dependencies and scripts
β βββ tsconfig.json # TypeScript configuration file
β
βββ kubernetes/ # Kubernetes configuration files
β βββ manifests/ # Kubernetes manifests for deployment, service, and ingress
β βββ backend-deployment.yaml # Deployment configuration for the backend
β βββ backend-service.yaml # Service configuration for the backend
β βββ frontend-deployment.yaml # Deployment configuration for the frontend
β βββ frontend-service.yaml # Service configuration for the frontend
β βββ firebase-deployment.yaml # Deployment configuration for Firebase
β βββ firebase-service.yaml # Service configuration for Firebase
β βββ configmap.yaml # ConfigMap configuration for environment variables
β
βββ nginx/
β βββ nginx.conf # NGINX configuration file for load balancing and caching
β βββ Dockerfile # Docker configuration file for NGINX
β
βββ images/ # Images for the README
βββ .env # Environment variables file for the whole app
βββ docker-compose.yml # Docker Compose file for containerization
βββ jsconfig.json # JavaScript configuration file
βββ package.json # Project dependencies and scripts
βββ package-lock.json # Lock file for dependencies
βββ postcss.config.js # PostCSS configuration file
βββ tailwind.config.js # Tailwind CSS configuration file
βββ render.yaml # Render configuration file
βββ vercel.json # Vercel configuration file
βββ openapi.yaml # OpenAPI specification for API documentation
βββ manage_docuthinker.sh # Shell script for managing and starting the app (both frontend & backend)
βββ jenkins_cicd.sh # Shell script for managing the Jenkins CI/CD pipeline
βββ .gitignore # Git ignore file
βββ LICENSE.md # License file for the project
βββ README.md # Comprehensive README for the whole app
βββ (and many more files...) # Additional files and directories not listed here
Ensure you have the following tools installed:
.env
file - but you should obtain your own API keys for production).Additionally, basic fullstack development knowledge and AI/ML concepts are recommended to understand the appβs architecture and functionalities.
Clone the repository:
git clone https://github.com/hoangsonww/DocuThinker-AI-App.git
cd DocuThinker-AI-App/backend
Navigate to the frontend directory:
cd frontend
Install dependencies:
npm install
Or npm install --legacy-peer-deps
if you face any peer dependency issues.
npm start
Build the Frontend React app (for production):
npm run build
yarn
to install dependencies and run the app:
yarn install
yarn start
Or, for your convenience, if you have already installed the dependencies, you can directly run the app in the root directory using:
npm run frontend
This way, you donβt have to navigate to the frontend
directory every time you want to run the app.
http://localhost:3000
. You can now access it in your browser.Note that this is optional since we are deploying the backend on Render. However, you can (and should) run the backend locally for development purposes.
backend
) directory:
cd backend
npm install
Or npm install --legacy-peer-deps
if you face any peer dependency issues.
npm run server
http://localhost:3000
. You can access the API endpoints in your browser or Postman.backend
directory. Feel free to explore the API endpoints and controllers.Note: Be sure to use Node v.20 or earlier to avoid compatibility issues with Firebase Admin SDK.
cd mobile-app
npm install
npx expo start
The backend of DocuThinker provides several API endpoints for user authentication, document management, and AI-powered insights. These endpoints are used by the frontend to interact with the backend server:
Method | Endpoint | Description |
---|---|---|
POST | /register |
Register a new user in Firebase Authentication and Firestore, saving their email and creation date. |
POST | /login |
Log in a user and return a custom token along with the user ID. |
POST | /upload |
Upload a document for summarization. If the user is logged in, the document is saved in Firestore. |
POST | /generate-key-ideas |
Generate key ideas from the document text. |
POST | /generate-discussion-points |
Generate discussion points from the document text. |
POST | /chat |
Chat with AI using the original document text as context. |
POST | /forgot-password |
Reset a userβs password in Firebase Authentication. |
POST | /verify-email |
Verify if a userβs email exists in Firestore. |
GET | /documents/{userId} |
Retrieve all documents associated with the given userId . |
GET | /documents/{userId}/{docId} |
Retrieve a specific document by userId and docId . |
GET | /document-details/{userId}/{docId} |
Retrieve document details (title, original text, summary) by userId and docId . |
DELETE | /delete-document/{userId}/{docId} |
Delete a specific document by userId and docId . |
DELETE | /delete-all-documents/{userId} |
Delete all documents associated with the given userId . |
POST | /update-email |
Update a userβs email in both Firebase Authentication and Firestore. |
POST | /update-password |
Update a userβs password in Firebase Authentication. |
GET | /days-since-joined/{userId} |
Get the number of days since the user associated with userId joined the service. |
GET | /document-count/{userId} |
Retrieve the number of documents associated with the given userId . |
GET | /user-email/{userId} |
Retrieve the email of a user associated with userId . |
POST | /update-document-title |
Update the title of a document in Firestore. |
PUT | /update-theme |
Update the theme of the app. |
GET | /user-joined-date/{userId} |
Get date when the user associated with userId joined the service. |
GET | /social-media/{userId} |
Get the social media links of the user associated with userId . |
POST | /update-social-media |
Update the social media links of the user associated with userId . |
POST | /update-profile |
Update the userβs profile information. |
POST | /update-document/{userId}/{docId} |
Update the document details in Firestore. |
POST | /update-document-summary |
Update the summary of a document in Firestore. |
POST | /sentiment-analysis |
Analyzes the sentiment of the provided document text |
POST | /bullet-summary |
Generates a summary of the document text in bullet points |
POST | /summary-in-language |
Generates a summary in the specified language |
POST | /content-rewriting |
Rewrites or rephrases the provided document text based on a style |
POST | /actionable-recommendations |
Generates actionable recommendations based on the document text |
GET | /graphql |
GraphQL endpoint for querying data from the database |
More API endpoints will be added in the future to enhance the functionality of the app. Feel free to explore the existing endpoints and test them using Postman or Insomnia.
http://localhost:5000/api-docs
.http://localhost:5000/api-docs/redoc
.For example, our API endpoints documentation looks like this:
Additionally, we also offer API file generation using OpenAPI. You can generate API files using the OpenAPI specification. Here is how:
npx openapi-generator-cli generate -i http://localhost:5000/api-docs -g typescript-fetch -o ./api
This will generate TypeScript files for the API endpoints in the api
directory. Feel free to replace or modify the command as needed.
openapi.yaml
Fileopenapi.yaml
file or paste its content.openapi.yaml
into Postman:
openapi.yaml
.npm install @openapitools/openapi-generator-cli -g
openapi-generator-cli generate -i openapi.yaml -g <language> -o ./client
<language>
with the desired programming language.openapi-generator-cli generate -i openapi.yaml -g <framework> -o ./server
<framework>
with the desired framework.npm install -g @stoplight/prism-cli
prism mock openapi.yaml
openapi.yaml
or paste its content to check for errors./upload
endpoint by sending a POST request with the document file as a form-data parameter.curl --location --request POST 'http://localhost:3000/register' \
--header 'Content-Type: application/json' \
--data-raw '{
"email": "test@example.com",
"password": "password123"
}'
curl --location --request POST 'http://localhost:3000/upload' \
--header 'Authorization: Bearer <your-token>' \
--form 'File=@"/path/to/your/file.pdf"'
The backend APIs uses centralized error handling to capture and log errors. Responses for failed requests are returned with a proper status code and an error message:
{
"error": "An internal error occurred",
"details": "Error details go here"
}
Our application supports a fully-featured GraphQL API that allows clients to interact with the backend using flexible queries and mutations. This API provides powerful features for retrieving and managing data such as users, documents, and related information.
https://docuthinker-ai-app.onrender.com/graphql
Or, if you are running the backend locally, the endpoint will be:
http://localhost:3000/graphql
Testing the API:
You can use the built-in GraphiQL Interface to test queries and mutations. Simply visit the endpoint in your browser.
You should see the following interface:
Now you can start querying the API using the available fields and mutations. Examples are below for your reference.
This query retrieves a userβs email and their documents, including titles and summaries:
query GetUser {
getUser(id: "USER_ID") {
id
email
documents {
id
title
summary
}
}
}
Retrieve details of a document by its ID:
query GetDocument {
getDocument(userId: "USER_ID", docId: "DOCUMENT_ID") {
id
title
summary
originalText
}
}
Create a user with an email and password:
mutation CreateUser {
createUser(email: "example@domain.com", password: "password123") {
id
email
}
}
Change the title of a specific document:
mutation UpdateDocumentTitle {
updateDocumentTitle(userId: "USER_ID", docId: "DOCUMENT_ID", title: ["Updated Title.pdf"]) {
id
title
}
}
Delete a document from a userβs account:
mutation DeleteDocument {
deleteDocument(userId: "USER_ID", docId: "DOCUMENT_ID")
}
errors
field in the response.For more information about GraphQL, visit the official documentation. If you encounter any issues or have questions, feel free to open an issue in our repository.
The DocuThinker mobile app is built using React Native and Expo. It provides a mobile-friendly interface for users to upload documents, generate summaries, and chat with an AI. The mobile app integrates with the backend API to provide a seamless experience across devices.
Currently, it is in development and will be released soon on both the App Store and Google Play Store.
Stay tuned for the release of the DocuThinker mobile app!
Below is a screenshot of the mobile app (in development):
The DocuThinker app can be containerized using Docker for easy deployment and scaling. Follow these steps to containerize the app:
docker compose up --build
You can also view the image in the Docker Hub repository here.
Install the Vercel CLI:
npm install -g vercel
Deploy the frontend:
vercel
Follow the instructions in your terminal to complete the deployment.
The backend can be deployed on platforms like Heroku, Render, or Vercel.
Currently, we are using Render to host the backend. You can access the live backend here.
Please note that we are currently on the Free Tier of Render. This means that the backend server may take a few seconds to wake up if it has been inactive for a while.
Therefore, the first API call may take a bit longer to respond. Subsequent calls should be faster as the server warms up. It is completely normal to take up to 2 minutes for the first API call to respond.
Also, the Free Tier of Render only allocates 512MB and 0.1 CPU. This may result in slower response times for API calls and document processing.
Additionally, during high traffic periods, the server may take longer to respond, although we have employed NGINX for load balancing and caching.
nginx
directory.Jenkinsfile
.brew install jenkins
brew services start jenkins
Access Jenkins:
Open your browser and go to http://localhost:8080
to access the Jenkins dashboard.
If successful, you should see the Jenkins pipeline running and deploying the app automatically whenever changes are pushed to the main branch. Here is an example:
kubernetes
directory.We welcome contributions from the community! Follow these steps to contribute:
Fork the repository.
git checkout -b feature/your-feature
git commit -m "Add your feature"
git push origin feature/your-feature
Thank you for contributing to DocuThinker! π
This project is licensed under the Creative Commons Attribution-NonCommercial License. See the LICENSE file for details.
The DocuThinker open-source project is for educational purposes only and should not be used for commercial applications. Feel free to use it for learning and personal projects!
For more information on the DocuThinker app, please refer to the following resources:
Here are some information about me:
Happy Coding and Analyzing! π
Created with β€οΈ by Son Nguyen in 2024.