Requirements
What a person, an administrator and a site need to use Virtik: a current browser with the features the application relies on, an authenticator app, and the connections each module depends on.
- Versione
- 0.2
- Ultimo aggiornamento
Sfoglia la documentazione
In questa pagina
Questo documento è attualmente pubblicato solo in inglese. Leggi la versione inglese di riferimento
This page lists what Virtik needs from the browser, the network and the site. It is drawn from what the application uses, not from a test matrix, and it says where that matters.
For everyone
- A current browser that supports modern JavaScript. The application does not check the browser version.
- WebGL. The maps, the 3D and 360° viewers need it. Where it is unavailable the camera's 360° viewer says "This browser cannot run the 360 viewer".
- Web Workers. The check that runs before sign-in prefers one and falls back to the main page if it cannot start.
- Cookies and local storage, for the signed-in session.
- A screen. The application adapts to narrow screens. Below 768 pixels it uses the compact layout, and many workspaces switch layout at 1,024 pixels.
- Installable. The web application can be added to a desktop or home screen.
For video
Live camera video is played through WebRTC where available, and through HLS otherwise. Both need a media gateway behind the cameras; see Cameras and data sources.
For administrators and editors
- An authenticator app that produces six-digit codes. Administrators and editors must enrol one. See Multi-factor authentication.
- An email address that can receive the confirmation and invitation messages.
For the network
The application reaches Virtik's backend over secure HTTPS and WebSocket connections, a map provider and its tile services, and other providers for weather, traffic and payment where those features are used. Which exact hosts are needed is confirmed for each deployment, so this page gives no host list. Video gateway hosts are specific to the deployment and are not covered by the application's own list. Browsers and firewalls must allow those connections, including secure WebSockets for live updates.
For cameras and sites
- Cameras that speak ONVIF or provide an RTSP stream, reachable from the site's Edge Connector or from the cloud, depending on the camera's address.
- Map access. The maps use a built-in public token unless the deployment overrides it. See Mapping.
For mobile
The mobile application needs a camera and a microphone for evidence, location for patrols and attendance, and notifications. It also asks for background ("always") location for automatic time in and out, where the organisation has location capture on. Access to the photo library is optional. It is not distributed through a store; see Mobile deployment. No minimum operating-system version is published.