File tree Expand file tree Collapse file tree 2 files changed +11
-2
lines changed Expand file tree Collapse file tree 2 files changed +11
-2
lines changed Original file line number Diff line number Diff line change @@ -75,7 +75,7 @@ It allows you to run several commands inside it.
75
75
76
76
.. code-block :: sh
77
77
78
- $ $ zammad run rails c
78
+ $ zammad run rails c
79
79
80
80
.. tab :: Source/Development Installation
81
81
Original file line number Diff line number Diff line change @@ -226,11 +226,12 @@ Build/rebuild the searchindex
226
226
.. hint ::
227
227
- The rebuild may take many hours or even days, if a lot of data is
228
228
already present in a productive environment. However, you can safely
229
- run this during operating times without the risk of loosing data. As a
229
+ run this during operating times without the risk of losing data. As a
230
230
downside, it could lead to reduced performance and that some data may
231
231
not be shown in search results.
232
232
- Consider specifying a number of CPU cores to be used for the rebuild
233
233
(see example below).
234
+ - If you just want to add a missing index, use the third command below.
234
235
235
236
.. code-block :: sh
236
237
@@ -240,6 +241,14 @@ Build/rebuild the searchindex
240
241
# rebuilding the searchindex, as in the following example with 8 cores:
241
242
$ sudo zammad run rake zammad:searchindex:rebuild[8]
242
243
244
+ Add a specific index with the command below. Replace ``Ticket `` with the one
245
+ you want to add. If your database already holds data which has to be indexed,
246
+ additionally use the second command:
247
+
248
+ .. code-block :: sh
249
+
250
+ $ zammad run rails r " SearchIndexBackend.create_object_index('Ticket')"
251
+ $ zammad run rails r " Ticket.search_index_reload"
243
252
244
253
Optional settings
245
254
-----------------
You can’t perform that action at this time.
0 commit comments