FLECS
HomeMarketplaceRessourcesGet started
Engineering
Engineering
  • API Docs
    • FLECS Console API
      • Welcome!
      • Quick Start
      • API Reference
        • Authentication
        • Users
        • Products
        • Device
        • Apps
    • FLECS Core API
      • API Reference
        • System
        • Device
        • Console
        • Instances
        • Apps
        • Jobs
  • App Publishing Guide
    • 💡Overview
    • 🪛How to create a FLECS app
    • 🚀How to release a FLECS app
    • 🧳App Publishing Packages
    • 📶Network
  • FLECS Core
    • Install FLECS Core Using Docker
  • White Labeling
    • Integrate views
    • On-premise hosting of apps
Powered by GitBook
On this page
  • Cloning the desired apps into a local docker registry
  • Customize the app manifest

Was this helpful?

  1. White Labeling

On-premise hosting of apps

PreviousIntegrate views

Last updated 2 months ago

Was this helpful?

There are environments that do not have direct internet access. For these environments, the FLECS apps can also be hosted on-premise. As an app consists of one or more docker images and the app , these two things are required:

Cloning the desired apps into a local docker registry

The FLECS docker registry can be easily synchronised with tools such as Crane to deploy the images in a private network without internet access. Access tokens to the required apps can be retreived from FLECS.

Customize the app manifest

Since the app manifests point to the FLECS registry, the pointer must be changed to the private registry in this case. To do this, change the image entry in the manifest and replace flecs.azurecr.io with <my local registry>. The modified manifest can then be made available to the FLECS Core either via the sideload or via its app installation API (FLECS Core API). The FLECS Core will then automatically attempt to pull the image from <my local registry>.

manifest.json