Skip to main content
0 of 5 lessons complete
View as Markdown

Setting Up Your Training Gateway

This section walks you through setting up your Kanoa MES training gateway: preparing the Ignition Gateway, creating the kanoaCore database connection and the Kanoa tag provider, installing the Kanoa MES module, and applying the recommended Gateway settings.

Quick Start with Docker​

If you have Docker installed, you can skip most of the manual setup. The kanoa-docker-template repository spins up a local training environment with Docker Compose:

  • An Ignition gateway with the Kanoa MES and Embr Charts modules installed
  • A SQL Server (Developer edition) database, created automatically on startup
  • The kanoaCore database connection, with Include Schema in Table Name enabled and Max Active set to -1
  • The Kanoa tag provider
Hands-on

  1. Click Use this template on the kanoa-docker-template GitHub page to create your own copy, then clone it. You can also clone the template repository directly.

  2. Copy the example environment file and set SA_PASSWORD in .env:

    cp .env.example .env

  3. Start the stack:

    docker compose up -d

  4. Open the gateway. By default the template routes it through a Traefik proxy at http://kanoa-dev.localtest.me. If you don't run Traefik, follow Option B in the template's README to expose it at http://localhost:8088 instead.

  5. On Config → Databases → Connections, confirm kanoaCore shows Valid. If it's faulted, edit the connection and set its password to your SA_PASSWORD.

With the Docker environment running, you can skip Prepare the Ignition Gateway, Configure the Database Connection, Configure the Tag Provider and Install the Kanoa MES Module. You still need to set the User Inactivity timeout described in Other Recommended Settings.

tip

On an Apple Silicon Mac, the standard SQL Server image doesn't run, it is recommended to use Rosetta emulation to run a standard image of SQL Server.

Warning / Caution

The Docker template is for development and training only. Running this SQL Server stack in production violates Microsoft SQL Server's licensing terms.

Last updated on