Skip to content

Akita Core

You can deploy Akita Core in many ways, including:

  • Windows
    • Command line utility
    • Windows Service
  • Linux
    • Command line utility
    • Linux daemon
  • Docker container

If you want to deploy Akita as Linux Daemon or Windows Service, follow these instructions. It should be possible to run Akita on MacOS, as well as other *ix systems, but we've never tested such a scenario.

In production environment docker container is a preferred deployment option.

Settings

You must set a variety of options for the application. Depending on the deployment scenario, you can do that either by setting environment variables or by editing application.properties file.

application.settings and environment variables

If you run the application as command line utility or or as a daemon (service), use application.properties. In case of docker deploy, then ENV file is preferred. Note that environment variables have higher priority.

Basic settings

Variable Default value Notes
AKITA_API_KEY MySuperS3cr3tKeyF0rTheSvc Mandatory
PUBLIC_PREFIXES /api/public Multi-valued key

Sales defaults

Variable Default value Notes
DEFAULT_SCHEMA 1 Mandatory
DEFAULT_LOCATION 1 Mandatory
DEFAULT_DOCTOR 1 Mandatory
DEFAULT_SPECIALTY 1 Mandatory

LIS iLab database connection

Variable Default value Notes
DB_URL jdbc:sqlserver://localhost;databaseName=iLab;encrypt=false; Mandatory
DB_USER sa Mandatory
DB_PASSWORD Secr3tPa$$w0rd Mandatory
DB_CLASS_NAME com.microsoft.sqlserver.jdbc.SQLServerDriver
DB_SHOW_SQL false

Cache

Under development

Example ENV file

# Basic settings
AKITA_API_KEY='MySuperS3cr3tKeyF0rTheSvc'
# Sales defaults
DEFAULT_SCHEMA=1
DEFAULT_LOCATION=1
DEFAULT_DOCTOR=1
DEFAULT_SPECIALTY=1
# Database settings
DB_URL='jdbc:sqlserver://localhost;databaseName=iLab;encrypt=true;trustServerCertificate=true;'
DB_USER='sa'
DB_PASSWORD='Secr3tPa$$w0rd'

Example docker command

In case of single-container deployment, you could run it with the following command (we assume you have ENV file named akita.env in current folder):

docker run --env-file ./akita.env -p 80:8080 --restart=unless-stopped -d skyware/akita:0.6.0

SSL, please

You probably would have some kind of reverse proxy that will handle SSL. Using Akita trough non encrypted http is GDPR and other regulations violation.

.