Skip to content

Client Setup

Install or Update

Use this procedure for regular client web deployment and updates.

  1. Rename existing <httpd-server>/htdocs/insight/mobile (backup).
  2. Extract insight-mobile-<version>.zip into <httpd-server>/htdocs/insight.

Example target:

<httpd-server>/htdocs/insight/mobile

Legacy insight-web Update (Deprecated from v36.0)

For existing installations still using Insight-Web:

  1. Rename existing <httpd-server>/htdocs/insight/web (backup).
  2. Extract insight-web-<version>.zip into <httpd-server>/htdocs/insight.

Migration note: - Keep /insight/web only as long as required for transition. - Move browser usage and links to /insight/client.

Configure /insight/client Alias

Expose /insight/client via reverse proxy and map it to /insight/mobile.

Apache (example)

## enable if not already enabled
RewriteEngine On

## configuration alias for client
RewriteRule ^insight/client(.*)$ /insight/mobile$1 [L]

Kubernetes Ingress (example)

Expose /insight/client via your ingress from the insight-client pod.

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
    name: insight-clients
spec:
    ingressClassName: nginx
    rules:
        - host: { { .Values.ingress.externalHostname } }
          http:
              paths:
                  - path: /insight/mobile
                    pathType: Prefix
                    backend:
                        service:
                            name: clients
                            port:
                                name: insight-clients
                  - path: /insight/client
                    pathType: Prefix
                    backend:
                        service:
                            name: clients
                            port:
                                name: insight-clients

Traefik (example)

- traefik.http.routers.clients.rule=Host(`${DOMAINNAME}`) && PathPrefix(`/insight/web`,`/insight/mobile`,`/insight/client`)

Validation After Deployment

  • Verify login and startup with /insight/mobile.
  • Verify browser entry with /insight/client.
  • If still in migration phase, verify /insight/web and plan its removal.