Config

LightHouse configuration is split into two categories:

• Static configuration — set in config.yaml and/or environment variables; requires a restart to change. See Static Configuration.
• Database-managed configuration — stored in the database, changed at runtime via the Admin API, lhsetup, or lhmigrate config2db; no restart required. See Database-Managed Configuration.

Both are needed!

Those are not alternative approaches! Both static and database-managed configuration is needed.

Configuration Sections

Static Configuration (Config File & Environment Variables)

• Static Configuration
• Server
• Logging
• Storage
• Cache
• Signing
• Admin API
• Statistics

Database-Managed Configuration

• Database-Managed Config
• Signing
• Entity Configuration
• Trust Marks
• Trust Anchors
• Federation Endpoints
• Subordinates

DB-Managed Configuration

Federation endpoints, trust anchors, metadata, authority hints, trust marks, signing algorithm, key rotation, and other runtime options are stored in the database. Use lhsetup for interactive setup, lhmigrate config2db for non-interactive migration from a config file, or the Admin API for runtime management.

Time Duration Configuration Options

Some configuration option take a duration, e.g. the lifetime of entity statements or the entity configuration.

There are different options how to pass a duration in the config file:

• Number: If only a number is given, this is the number of seconds.
• String: The duration can also be given as a string which supports different units.

For a duration string the following units are supported and multiple units can be used in a single string:

Symbol	Unit	Comment
y	Year	= 365 days
w	Week	= 7 days
d	Day	= 24 hours
h	Hour
m	Minute
s	Second
ms	Millisecond	SHOULD NOT be used
µs	Microsecond	SHOULD NOT be used
ns	Nanosecond	SHOULD NOT be used

Examples

1y
2w6d
20d
1h30m