You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,11 @@ Global.configure do |config|
33
33
end
34
34
```
35
35
36
+
### Using multiple backends
37
+
38
+
Sometimes it is practical to store some configuration data on disk (and perhaps, commit it to source control), but
39
+
keep some other data in a secure remote location. Which is why you can use more than one backend with Global.
40
+
36
41
You can declare as many backends as you want; the configuration trees from the backends are deep-merged together,
37
42
so that the backend declared later overwrites specific keys in the backend declared prior:
38
43
@@ -322,12 +327,6 @@ Get configuration in the app:
322
327
=> "https://api.myapp.com"
323
328
```
324
329
325
-
326
-
### Combining stores
327
-
328
-
Sometimes it is practical to store some configuration data on disk, and some in AWS Parameter Store or in Google Cloud Secret Manager; you can declare both backends, and configuration
329
-
will be merged (declaration order influence on configuration merge).
0 commit comments