Application Deployment

For production environments, we recommend a Manual Binary Deployment managed by Systemd (Linux) or Windows Services.

Why?

1. Process Control: We rely on OS-level signals (SIGINT) for Graceful Shutdowns. If you restart a server, the app will stop accepting new calls but keep active calls alive until they finish. Docker often kills processes too aggressively.
2. Audio Latency: Running natively ensures RTP packets reach the kernel immediately without NAT overhead.

1. Getting the Artifacts

Download the latest .zip release from our GitHub repository or build from source.

• iqra-frontend-linux-x64.zip
• iqra-proxy-linux-x64.zip
• iqra-backend-linux-x64.zip
• iqra-background-linux-x64.zip

Recommended Directory Structure:

/opt/iqra/
  ├── frontend/
  ├── proxy/
  ├── backend/
  └── background/

2. Deployment Order (Critical)

You cannot simply turn everything on at once. The system has a strict dependency chain.

1. Frontend: Must run first to seed the database and create the Admin account.
2. Initialization: You must log in and register the server topology.
3. Workers: Only then can the Backend and Proxy start (they check the registry on boot).

Step 1: Deploy Frontend

[Unit]
Description=Iqra AI Frontend
After=network.target

[Service]
WorkingDirectory=/opt/iqra/frontend
ExecStart=/opt/iqra/frontend/ProjectIqraFrontend
Restart=always
RestartSec=10
User=root
Environment=ASPNETCORE_ENVIRONMENT=Production
Environment=ASPNETCORE_URLS=http://localhost:5000

[Install]
WantedBy=multi-user.target

sudo systemctl enable --now iqra-frontend

Step 2: Reverse Proxy (SSL)

We recommend running all services behind Nginx to handle SSL and WebSockets securely.

# 1. Frontend (Dashboard)
server {
    listen 443 ssl http2;
    server_name app.your-domain.com;
    # ... SSL Params ...

    location / {
        proxy_pass http://localhost:5000;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }
}

# 2. Proxy App (Telephony Webhooks)
server {
    listen 443 ssl http2;
    server_name proxy.your-domain.com;
    # ... SSL Params ...

    location / {
        proxy_pass http://localhost:5001;
    }
}

🛑 Step 3: The Critical Pause

Step 4: Deploy Worker Nodes

For Proxy, Backend, and Background, follow the same installation pattern as the Frontend, but with specific configurations.

Configuration Checklist

Ensure appsettings.json matches the values you just generated in the Admin Dashboard.

Service Templates (Systemd)

Use this template for Proxy, Backend, and Background. Just change the Description, WorkingDirectory, ExecStart, and Port.

[Unit]
Description=Iqra AI Backend
After=network.target

[Service]
WorkingDirectory=/opt/iqra/backend
ExecStart=/opt/iqra/backend/ProjectIqraBackendApp
Restart=always
RestartSec=10

# Graceful Shutdown Logic
# 1. Send SIGINT (App stops accepting new calls)
KillSignal=SIGINT
# 2. Wait 10 Minutes for active calls to finish
TimeoutStopSec=600

User=root
Environment=ASPNETCORE_ENVIRONMENT=Production
# Use different internal ports for each app (e.g. 5002 for Backend)
Environment=ASPNETCORE_URLS=http://localhost:5002

[Install]
WantedBy=multi-user.target

Port Mapping Recommendation:

• Frontend: 5000
• Proxy: 5001
• Backend: 5002
• Background: 5003

Firewall Rules

You must open ports for external traffic.