Folder Layout

TEDI is organized into the following folders and requires they exist:

---

tedi
├── bin
│   ├── start.sh
│   ├── stop.sh
├── block
├── conf
│   ├── account.properties
│   ├── alert.properties
│   ├── certmanager.properties
│   ├── docker-compose.yml
│   ├── http.properties
│   ├── keymanager.properties
│   ├── logger.properties
│   ├── nats.properties
│   ├── nats_connections.properties
│   ├── nats_kvs.properties
│   ├── purging.properties
│   ├── server.properties
│   └── sql.datasources.properties
├── data
├── keys
├── logs
├── services
├── system
└── utils

---

bin

the bin directory stores files that are executable.

for example, scripts to bootstrap TEDI, the TEDI binaries, etc.

block

the block directory is used to store block files. Block files are a means to quickly disable an integration(s) from running.

For example, if you create an integration named toybox.logistics and you wanted to temporarily disable that integration, you could create a file called toybox.logistics.block and that would disable the service until removed.

conf

The conf directory is where TEDI stores its configuration files. The individual files, and the purpose of them, will be covered in another section.

data

The data directory is where TEDI writes content it operates on during an integration workflow.

keys

The keys directory is where TEDI expects certificates, keys (for encryption, etc), and ca-trustbundles.

logs

The logs directory is where TEDI stores its logs.

services

The services directory is where you will configure all of your integration workflows.

system

The system directory stores various configuration items for TEDI.

utils

The utils directory stores various helper utilities for TEDI.