Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue #26: Document configuration file name extensions and loading rules recursively #79

Merged
merged 1 commit into from
Oct 28, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down