Before installing Quality Management System, ensure that your server meets the following requirements:

Prerequisites for IIS

• Windows Server 2019 or later / Windows 10/11
• IIS 10.0 or later
• .NET 8 Hosting Bundle
• SQL Server or SQL Server Express

Step 1: Install .NET 8 Hosting Bundle

1. Download the .NET 8 Hosting Bundle from Microsoft's official website
2. Run the installer as Administrator
3. Restart IIS after installation: iisreset

Step 2: Enable IIS Features

Open PowerShell as Administrator and run:

Enable-WindowsOptionalFeature -Online -FeatureName IIS-WebServerRole, IIS-WebServer, IIS-CommonHttpFeatures, IIS-HttpErrors, IIS-HttpRedirect, IIS-ApplicationDevelopment, IIS-NetFxExtensibility45, IIS-HealthAndDiagnostics, IIS-HttpLogging, IIS-Security, IIS-RequestFiltering, IIS-Performance, IIS-WebServerManagementTools, IIS-ManagementConsole, IIS-IIS6ManagementCompatibility, IIS-Metabase, IIS-ASPNET45

Step 3: Create Application Pool

1. Open IIS Manager
2. Right-click Application Pools → Add Application Pool
3. Name: QMS_Pool
4. .NET CLR Version: No Managed Code
5. Managed Pipeline Mode: Integrated
6. Click OK
7. Right-click the new pool → Advanced Settings
8. Set Identity to ApplicationPoolIdentity
9. Set Load User Profile to True

Step 4: Deploy Application Files

• Extract the QMS application files to C:\inetpub\wwwroot\QMS
• Ensure the IIS_IUSRS group has read and execute permissions on the folder
• Grant full control to the application pool identity on the following folders:
  • wwwroot
  • Logs
  • Temp

Step 5: Create Website in IIS

1. Right-click Sites → Add Website
2. Site name: QMS
3. Application pool: QMS_Pool
4. Physical path: C:\inetpub\wwwroot\QMS
5. Binding: HTTP, Port 80 (or HTTPS 443 with SSL certificate)
6. Host name: qms.yourdomain.com

Step 6: Configure Database Connection

Edit the appsettings.json file in the application root:

{
  "ConnectionStrings": {
    "DefaultConnection": "server=localhost;port=3306;user=root;password='';database=qms_db;AllowPublicKeyRetrieval=True;SslMode=None;"
  }
}

1. Set up SSL Certificate:

   Configure SSL/TLS certificates for HTTPS support using Let's Encrypt or commercial certificates

2. Configure Firewall:

   Open necessary ports (80, 443) and restrict access to the application port (5000) from external sources

3. Set up Monitoring:

   Configure application logging and monitoring for production environments

Tesseract OCR Installation for Window OS Server

1. Download the Tesseract Installer:
   Visit the official UB Mannheim GitHub page and download
   
   👉 tesseract-ocr-w64-setup-v5.2.0.20220708.exe
2. Install Tesseract:
   Run the installer and follow the prompts. During setup:
   • Select your language packs (at minimum, keep eng checked for English).
   • Ensure the option to add Tesseract to the system PATH is selected.
3. Verify PATH Configuration (if not set automatically):
   • Go to System Properties → Advanced → Environment Variables.
   • Under "System variables", select Path → click Edit.
   • Add this path (if not already there):
     C:\Program Files\Tesseract-OCR
   • Click OK to save and close all dialogs.
4. Verify Installation:
   Open Command Prompt and run:
   

   tesseract -v

   You should see the installed version and copyright.
5. Application Setup:
   Make sure your application has a tessdata folder placed inside the wwwroot directory.
   Example path: C:\\inetpub\\wwwroot\\{{yoursitename}}\\wwwroot\\tessdata
6. Set Folder Permissions:
   Grant full read/write permissions to the application pool identity or service user (IIS_IUSRS) running your web app:
   • Ensure read access to tesseract.exe.
   • Ensure read/write access to the C:\\inetpub\\wwwroot\\{{yoursitename}}\\tessdata folder to user IIS_IUSRS.
   • If hosted on a shared/VPS platform, confirm additional restrictions with your provider.
7. Test Tesseract OCR:
   To check if OCR works correctly, run this in the Command Prompt:

   tesseract path\to\image.png output-text-file -l eng

   • Replace path\to\image.png with the actual image path.
   • The output will be saved as output-text-file.txt.
8. Restart the IIS server

Prerequisites for Nginx

• Ubuntu 20.04+ / CentOS 8+ / RHEL 8+
• Nginx 1.18+
• .NET 8 Runtime
• SQL Server or MySQL

Step 1: Install .NET 8 Runtime

For Ubuntu/Debian:

wget https://packages.microsoft.com/config/ubuntu/20.04/packages-microsoft-prod.deb -O packages-microsoft-prod.deb
sudo dpkg -i packages-microsoft-prod.deb
sudo apt-get update
sudo apt-get install -y aspnetcore-runtime-8.0

For CentOS/RHEL:

sudo dnf install aspnetcore-runtime-8.0

Step 2: Install and Configure Nginx

sudo apt update
sudo apt install nginx
sudo systemctl start nginx
sudo systemctl enable nginx

Step 3: Deploy Application

1. Create application directory: sudo mkdir -p /var/www/qms
2. Extract application files to /var/www/qms
3. Set proper permissions:

   sudo chown -R www-data:www-data /var/www/qms
   sudo chmod -R 755 /var/www/qms
   sudo chmod -R 777 /var/www/qms/wwwroot
   sudo chmod -R 777 /var/www/qms/Logs
   sudo chmod -R 777 /var/www/qms/Temp

Step 4: Configure Nginx Virtual Host

Create /etc/nginx/sites-available/qms

server {
    listen 80;
    server_name qms.yourdomain.com;
    
    location / {
        proxy_pass http://localhost:5000;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection keep-alive;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_cache_bypass $http_upgrade;
    }
    
    # Static files
    location ~* \.(css|js|png|jpg|jpeg|gif|ico|svg)$ {
        root /var/www/qms/wwwroot;
        expires 1y;
        add_header Cache-Control "public, immutable";
    }
}

Step 5: Enable Site and Test

sudo ln -s /etc/nginx/sites-available/qms /etc/nginx/sites-enabled/
sudo nginx -t
sudo systemctl reload nginx

Step 6: Create Systemd Service

Create /etc/systemd/system/qms.service

[Unit]
Description=QMS .NET Web API
After=network.target

[Service]
Type=notify
ExecStart=/usr/bin/dotnet /var/www/qms/QMS.dll
Restart=always
RestartSec=5
KillSignal=SIGINT
SyslogIdentifier=qms
User=www-data
Environment=ASPNETCORE_ENVIRONMENT=Production
Environment=DOTNET_PRINT_TELEMETRY_MESSAGE=false
WorkingDirectory=/var/www/qms

[Install]
WantedBy=multi-user.target

Enable and start the service:

sudo systemctl daemon-reload
sudo systemctl enable qms.service
sudo systemctl start qms.service
sudo systemctl status qms.service

Tesseract OCR Installation for Linux

1. Update your system: sudo apt update sudo apt upgrade
2. Install Tesseract OCR:

   sudo apt install tesseract-ocr

3. Install languages (optional):

   sudo apt install tesseract-ocr-eng
   sudo apt install tesseract-ocr-[lang]

4. Verify installation:

   tesseract -v

5. Create tessdata directory (if needed):

   mkdir -p /var/www/{{yoursitename}}/wwwroot/tessdata

6. Set permissions:

   sudo chmod -R 755 /var/www/{{yoursitename}}/wwwroot/tessdata

7. Manual OCR Test (optional):

   tesseract /path/to/image.png output-text -l eng

8. Install dependencies:

   sudo apt-get install -y libtesseract-dev libleptonica-dev

9. Verify library files:

   find /usr -name "libtesseract.so*"
   find /usr -name "libleptonica.so*"

10. Copy to x64 directory in project:

    
    cp /usr/lib/x86_64-linux-gnu/libtesseract.so* /var/www/{{yoursitename}}/x64/
                                

    
    cp /usr/lib/x86_64-linux-gnu/libleptonica.so* /var/www/{{yoursitename}}/x64/
                              

    
    or use /usr/local/lib/ path if applicable.
11. Set LD_LIBRARY_PATH globally:

    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/var/www/{{yoursitename}}/x64/
    source ~/.bashrc

    Or edit:

    sudo nano /etc/environment
    LD_LIBRARY_PATH="/var/www/{{yoursitename}}/x64/:$LD_LIBRARY_PATH"

12. Compatible Versions:
    • Tesseract 5.2.0
    • libtesseract 5.2.x
    • libleptonica 1.82.0+
13. Restart services:

    sudo systemctl restart {{yoursitename}}.service
    sudo systemctl restart nginx

1. Set up SSL Certificate:

   Configure SSL/TLS certificates for HTTPS support using Let's Encrypt or commercial certificates

2. Configure Firewall:

   Open necessary ports (80, 443) and restrict access to the application port (5000) from external sources

3. Set up Monitoring:

   Configure application logging and monitoring for production environments

Prerequisites for Apache

• Apache 2.4+
• .NET 8 Runtime
• mod_proxy and mod_proxy_http modules
• SQL Server or MySQL

Step 1: Install .NET 8 Runtime

Follow the same .NET installation steps as described in the Nginx section above.

Step 2: Install and Configure Apache

For Ubuntu/Debian:

sudo apt update
sudo apt install apache2
sudo a2enmod proxy
sudo a2enmod proxy_http
sudo a2enmod headers
sudo systemctl restart apache2

Step 3: Deploy Application

Follow the same deployment steps as described in the Nginx section.

Step 4: Configure Apache Virtual Host

Create /etc/apache2/sites-available/qms.conf

<VirtualHost *:80>
    ServerName qms.yourdomain.com
    DocumentRoot /var/www/qms/wwwroot
    
    ProxyPreserveHost On
    ProxyPass /api/ http://localhost:5000/api/
    ProxyPassReverse /api/ http://localhost:5000/api/
    ProxyPass / http://localhost:5000/
    ProxyPassReverse / http://localhost:5000/
    
    # Headers for better proxy support
    ProxyPassReverse / http://localhost:5000/
    RequestHeader set X-Forwarded-Proto "http"
    RequestHeader set X-Forwarded-Port "80"
    
    # Static files handling
    Alias /wwwroot /var/www/qms/wwwroot
    <Directory "/var/www/qms/wwwroot">
        AllowOverride None
        Require all granted
    </Directory>
    
    ErrorLog ${APACHE_LOG_DIR}/qms_error.log
    CustomLog ${APACHE_LOG_DIR}/qms_access.log combined
</VirtualHost>

Step 5: Enable Site and Restart Apache

sudo a2ensite qms.conf
sudo apache2ctl configtest
sudo systemctl reload apache2

Step 6: Create Systemd Service

Use the same systemd service configuration as described in the Nginx section.

SQL Server Configuration

1. Create a new database named QMS_DB
2. Create a database user with appropriate permissions
3. Update the connection string in appsettings.json

   "ConnectionStrings": {
     "DefaultConnection": "server=localhost;port=3306;user=root;password='';database=qms_db;AllowPublicKeyRetrieval=True;SslMode=None;"
   }

MySQL Configuration (Alternative)

1. Install MySQL server and create database
2. Update connection string for MySQL:

   "ConnectionStrings": {
     "DefaultConnection": "server=localhost;port=3306;user=root;password='';database=qms_db;AllowPublicKeyRetrieval=True;SslMode=None;"
   }

Tesseract OCR Installation for Linux

1. Update your system:

   sudo apt update
   sudo apt upgrade

2. Install Tesseract OCR:

   sudo apt install tesseract-ocr

3. Install languages (optional):

   sudo apt install tesseract-ocr-eng
   sudo apt install tesseract-ocr-[lang]

4. Verify installation:

   tesseract -v

5. Create tessdata directory (if needed):

   mkdir -p /var/www/{{yoursitename}}/wwwroot/tessdata

6. Set permissions:

   sudo chmod -R 755 /var/www/{{yoursitename}}/wwwroot/tessdata

7. Manual OCR Test (optional):

   tesseract /path/to/image.png output-text -l eng

8. Install dependencies:

   sudo apt-get install -y libtesseract-dev libleptonica-dev

9. Verify library files:

   find /usr -name "libtesseract.so*"
   find /usr -name "libleptonica.so*"

10. Copy to x64 directory in project:

    
    cp /usr/lib/x86_64-linux-gnu/libtesseract.so* /var/www/{{yoursitename}}/x64/
                                

    
    cp /usr/lib/x86_64-linux-gnu/libleptonica.so* /var/www/{{yoursitename}}/x64/
                              

    
    or use /usr/local/lib/ path if applicable.
11. Set LD_LIBRARY_PATH globally:

    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/var/www/{{yoursitename}}/x64/
    source ~/.bashrc

    Or edit:

    sudo nano /etc/environment
    LD_LIBRARY_PATH="/var/www/{{yoursitename}}/x64/:$LD_LIBRARY_PATH"

12. Compatible Versions:
    • Tesseract 5.2.0
    • libtesseract 5.2.x
    • libleptonica 1.82.0+
13. Restart services:

    sudo systemctl restart {{yoursitename}}.service
    sudo systemctl restart nginx

1. Set up SSL Certificate:

   Configure SSL/TLS certificates for HTTPS support using Let's Encrypt or commercial certificates

2. Configure Firewall:

   Open necessary ports (80, 443) and restrict access to the application port (5000) from external sources

3. Set up Monitoring:

   Configure application logging and monitoring for production environments

We're excited to announce the latest upgrade to our Document Management system: seamless integration with Amazon S3 storage. With this new feature, users can now enjoy enhanced flexibility and reliability in storing their documents. By leveraging Amazon S3, one of the most trusted cloud storage solutions available, users can upload their documents with confidence, knowing that their data is securely stored and easily accessible whenever they need it. This integration opens up a world of possibilities for efficient document management, allowing users to take advantage of Amazon's scalable infrastructure to handle their growing document storage needs.

In order to configure the Amazon S3 storage, you will need to setup the S3 bucket, and then configure the Document Management System to use the Amazon S3 storage.

Configure Storage(Settings -> Storage Settings)

Welcome! This user manual provides a clear, step-by-step guide on how to configure Gmail and Microsoft SMTP for sending emails from your application. Following this guide ensures a secure and reliable email setup.

Step 1: Enable 2-Step Verification

1. Open your Google Account Security page: https://myaccount.google.com/security

2. Under "Signing in to Google", enable 2-Step Verification (2FA).

3. Complete the setup using your mobile device. This step is required to generate a secure App Password for your application.

Step 2: Generate an App Password

1. After enabling 2FA, visit: https://myaccount.google.com/apppasswords

2. Configure the app password settings:

• App: Mail
• Device: Other (Custom Name) → enter a descriptive name like MyApp SMTP

3. Click Generate and copy the 16-character password displayed. Example:

abcd efgh ijkl mnop

This App Password will be used instead of your normal Gmail password for your application.

Step 3: Gmail SMTP Settings

Use the following SMTP settings in your backend application (Laravel, .NET, Node.js, etc.):

After configuring these settings, your application should be able to send emails securely using Gmail SMTP.

This guide explains how to configure your Microsoft (Outlook / Office 365) account to send emails from your application securely. Please follow these steps carefully to ensure a successful setup.

Step 1: Check Account Type and Permissions

Microsoft accounts require proper authentication to send emails via SMTP. Please ensure:

• Your account is either personal Outlook or Office 365 / Microsoft 365.
• You have access to the account's security settings.
• Your account is allowed to use SMTP (for Office 365, the admin may need to enable SMTP AUTH).

Step 2: Decide Authentication Method

There are two ways to authenticate when sending emails:

• App Password (Legacy / Personal Accounts): Works only if 2FA is enabled and your account allows app passwords.
• OAuth2 / Modern Authentication: Recommended for Office 365 or business accounts; secure and compliant with Microsoft policies.

Step 3: Microsoft SMTP Settings

Use the following SMTP settings in your application backend (Laravel, .NET, Node, etc.):

Step 4: Test Your Configuration

Once SMTP is configured, test sending an email from your application to ensure everything is working correctly. Check the inbox and spam folder to confirm delivery.

Step 5: Troubleshooting

• If email fails, check that SMTP AUTH is enabled for your account.
• Verify your firewall or hosting provider is not blocking port 587/465.
• For OAuth2, ensure your token is valid and hasn’t expired.

Configure Storage(Settings -> General Settings -> Open AI API Key)

Configure Storage(Settings -> General Settings -> Google Gemini API Key)

PDF preview

Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "application/octet-stream". Strict MIME type checking is enforced for module scripts per HTML spec.

This error is caused by the server not serving the PDF file with the correct MIME type. To fix this issue, you will need to add the following code to your server configuration file.

IIS (web.config):

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <system.webServer>
        <staticContent>
            <mimeMap fileExtension=".mjs" mimeType="text/javascript" />
            <mimeMap fileExtension=".ftl" mimeType="text/plain" />
        </staticContent>
    </system.webServer>
</configuration>

NGINX requires this configuration:

http  {
        ...
            types {
                    text/javascript mjs;
                    text/plain ftl;
					text/javascript js;
                }
	  }

APPACHE requires this configuration:

.htaccess file or extend your Apache config file with the following htaccess

<IfModule mod_mime.c>
         AddType text/javascript mjs
         AddType text/plain ftl
</IfModule>

AWS amplify requires this configuration in the amplify.yaml file:

customHeaders:
    - pattern: '*.mjs'
      headers:
        - key: 'Content-Type'
          value: 'application/javascript'
    - pattern: '*.ftl'
      headers:
          - key: 'Content-Type'
            value: 'text/plain'
  

Apache Logs

Apache errors (including permission errors or misconfigured virtual hosts) are typically found in:

Ensure mod_rewrite is enabled and your virtual host configuration allows overriding with `.htaccess`.

Nginx Logs

Nginx error logs (useful for Laravel routing or permission issues) are located at:

Make sure your Nginx server block (site config) points to the /public folder and the correct PHP version is referenced in the fastcgi_pass

Angular Development Errors

When developing the frontend (Angular), open your browser’s developer console (F12) to see errors and warnings. These usually help with:

• Missing modules or dependencies
• API request errors (check network tab)
• Routing or component loading issues

If errors occur during development build, run:

Installation .NET REST API in Local System steps

• Open solution file QualityManagement.sln from .Net folder into visual studio 2022.
• Right click on solution explorer and Restore nuget packages.
• Change database connection string in appsettings.Development.json in QualityManagement.API project.
• Open package manager console from visual studio menu --> Tools --> nuget Package Manager --> Package Manager Console
• In package manager console, Select default project as QualityManagement.Domain
• Run Update-Database command in package manager console which create database and insert intial data.
• From Solution Explorer, Right click on QualityManagement.API project and click on Set as Startup Project from menu.
• To run project Press F5.

Angular Local System

• To run a local copy in development mode, replace REST API URI (apiUrl) variable in environment file inside src --> environments -->environment.ts
• opens a terminal
• run npm install -f command
• run npm start command. which will runs the UI at http://localhost:4200/

We hope this documentation has helped you successfully set up and use the Quality Management System System. If you’ve found this product valuable, please consider showing your support by leaving a 5-star rating on CodeCanyon. ⭐⭐⭐⭐⭐

Your positive feedback not only motivates us to keep improving but also helps other users make confident decisions.

If you encounter any issues or need assistance, feel free to reach out through our support portal. We’re here to help!

June 23 - Initial Release