Skip to main content

15. Self Hosted Edge App: Advanced & Legacy Configuration

Advanced configuration for Self Hosted Edge App

Most installs should follow the standard flow in Self host our Edge Solution.
​
This article is for two situations: an install that uses a Client ID and Client Secret (connections set up before the install-token flow, or scripted installs arranged with our support), and changing how often the device checks for configuration updates.

Legacy: manual credential setup (deprecated, still supported)

If you already have a long-lived Client ID and Client Secret (from before the install-token flow, or provided by our support for a scripted install; contact [email protected]), you can pass them directly instead of using the install command's embedded token. Add to /etc/environment before installing:

MBAI_EDGE_CLIENT_ID=YOUR_CLIENT_ID
MBAI_EDGE_CLIENT_SECRET=YOUR_CLIENT_SECRET

Then install without the token:

sudo dpkg -i mbai-edge-native-<env>-<version>.deb

This still works, but the install command's embedded token (see Self host our Edge Solution, Installation) is the current recommended path for new installs - it needs no manual credential handling.

Advanced: overriding the check-in interval

MBAI_EDGE_POLL_INTERVAL controls how often (in seconds) the device checks in for configuration updates. The default and minimum is 60 seconds; smaller values are ignored. To use a longer interval, add to /etc/environment:

MBAI_EDGE_POLL_INTERVAL=<seconds>

If Edge App is already installed, apply the change with the command in Self host our Edge Solution → "Environment updates". A reinstall is not needed.

Did this answer your question?