Configuration

Where to keep your configuration and how services read it.

Get started

Keep your own values in .ini files that services read through self.config - hot-reloaded, editable in the dashboard and behaving like Python dictionaries.

Where to keep API configuration

Keep values in files

Configuration files Endpoints, mapping tables and business values in .ini files, read as self.config with dot access. Config tables Translate and validate the codes each party you integrate with uses for the same things. Environment variables The reference of environment variables - ports, databases, passwords and platform settings.

Work in the dashboard

Config tables in the dashboard Edit, check and save the files on one screen, with a lookup strip that answers before you save. Config tables and self.config What you save on the screen is what services read, live everywhere with no restarts in between.

Know what goes where

Configuration, enmasse and backups Three different questions with three different answers, and which one you are really asking. GitOps with enmasse Channels, connections and security are the environment's definition, exported and imported as YAML. Backup A backup preserves one installation, enmasse and git recreate an environment anywhere.