From 8e22670565458720111d8c6a77e7d55d153ee833 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marko=20Dimja=C5=A1evi=C4=87?= Date: Mon, 28 Oct 2019 11:50:09 +0100 Subject: [PATCH] Issue #26: document configuration file name extensions and loading rules recursively --- README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README.md b/README.md index 2ee5a97..c088971 100644 --- a/README.md +++ b/README.md @@ -280,6 +280,13 @@ At least, this is according to our understanding of the logic in the Go code. Ideally we should test this against `lyft/ratelimit` itself, which is a pending task. +Keep in mind that Fencer can load configuration from any YAML files +and not just files with the `.yml` extension. For example, Fencer will +load configuration from a YAML file named `limit` so long as the file +is located in the runtime directory given with the +`RUNTIME_SUBDIRECTORY` environment variable. Furthermore, it will load +configuration from a runtime subdirectory recursively, thereby +traversing the whole subdirectory. ## Differences to Lyft's rate limit service