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
Because you probably have more than one environment type that you're running search on (e.g. Production and UAT), and (generally speaking) you should have different engines for each of those environments. So, you can't just hardcode the entire engine name into your project, because that code doesn't change between environments.
66
66
67
-
Whenever you make a query, Forager will ask you for the "index" name; you will actually want to provide only the `<suffix>`. We will then take `BIFROST_ENGINE_PREFIX` and your `<suffix>`, put them together, and that's what will be queried. This allows you to set `BIFROST_ENGINE_PREFIX` differently for each environment, while having your `<suffix>` hardcoded in your project.
67
+
Whenever you make a query, Forager will ask you for the "index" name; you will actually want to provide only the `<engineSuffix>`. We will then take `BIFROST_ENGINE_PREFIX` and your `<engineSuffix>`, put them together, and that's what will be queried. This allows you to set `BIFROST_ENGINE_PREFIX` differently for each environment, while having your `<engineSuffix>` hardcoded in your project.
68
68
69
69
## Configuration
70
70
@@ -84,7 +84,7 @@ You can specify these data types in the `options` node of your fields.
84
84
```yaml
85
85
SilverStripe\Forager\Service\IndexConfiguration:
86
86
indexes:
87
-
<suffix>:
87
+
<engineSuffix>:
88
88
includeClasses:
89
89
SilverStripe\CMS\Model\SiteTree:
90
90
fields:
@@ -123,7 +123,7 @@ This field needs to contain a base 64 encoded string of binary for the file you
0 commit comments