File tree Expand file tree Collapse file tree 2 files changed +2
-11
lines changed Expand file tree Collapse file tree 2 files changed +2
-11
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 @@ -284,12 +284,11 @@ Build/rebuild the searchindex
284
284
.. hint ::
285
285
- The rebuild may take many hours or even days, if a lot of data is
286
286
already present in a productive environment. However, you can safely
287
- run this during operating times without the risk of losing data. As a
287
+ run this during operating times without the risk of loosing data. As a
288
288
downside, it could lead to reduced performance and that some data may
289
289
not be shown in search results.
290
290
- Consider specifying a number of CPU cores to be used for the rebuild
291
291
(see example below).
292
- - If you just want to add a missing index, use the third command below.
293
292
294
293
Without specifying CPU cores:
295
294
@@ -303,14 +302,6 @@ Build/rebuild the searchindex
303
302
304
303
$ sudo zammad run rake zammad:searchindex:rebuild[8]
305
304
306
- Add a specific index with the command below. Replace ``Ticket `` with the one
307
- you want to add. If your database already holds data which has to be indexed,
308
- additionally use the second command:
309
-
310
- .. code-block :: sh
311
-
312
- $ zammad run rails r " SearchIndexBackend.create_object_index('Ticket')"
313
- $ zammad run rails r " Ticket.search_index_reload"
314
305
315
306
Optional settings
316
307
-----------------
You can’t perform that action at this time.
0 commit comments