Configuration

This document explains 3 parts of the Vyndara Platform Configuration handling.

Configuration Handling

Each system based on the go-orm library uses the organization contexts. This provides a out of the box organization and application handling.

Each application has a internal organization, which is the organization configuration of the complete Vyndara Platform instance and can handle adjustments for the whole cluster.

A application can be configured with environment variables having the following:

ORGANIZATION_TIMEOUT = When a organization is invalidated after not being accessed in this time, in seconds. Default 30 Minutes.

ORGANIZATION = A organization name which needs to be present in the vault storage. Application starts with this application only and so on has no invalidation

Tenant Configuration (Organization)

Each tenant can configure on organization level by default a Database, Auth and Cache.

Available at the moment is:

Database:

• PostgreSQL

Cache:

• Redis

Auth:

• Arematics Auth
• Microsoft Entra ID (Phase 2)

Application Configuration

Each tenant can configure also multiple applications. That can have a database and a cache, auth needs to be configured with the tenants auth and roles. Multiple auths per organization is not possible and also considered as not required.

Other database can also mean same database but with another schema.

Configuration setup & usage

The configuration setup is done when a organization uses its license to setup a vyndara instance.

There it is possible to configure a database, auth and cache for the organization level. Database and Cache can be changed later on.

Also it is possible afterwards to setup applications after that directly, but also later on if wanted. Free users cant setup applications, they are limited to a organization

Each organization has its own unique name that should be passed to api requests. Applications get random ids that can also be passed to requests to get application specific configurations.