|
16.
|
|
|
delete all users that have never logged in, i.e. that were created manually, via CSV file, or an automated process;
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/cli.rst:47
|
|
17.
|
|
|
and / or delete all users that have not logged in since a certain date;
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/cli.rst:48
|
|
18.
|
|
|
and / or delete only those users from a specific institution;
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/cli.rst:49
|
|
19.
|
|
|
delete users that are members of a specific group.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/cli.rst:50
|
|
20.
|
|
|
``sudo -u www-data php htdocs/admin/cli/delete_inactive_users.php``
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/cli.rst:68
|
|
21.
|
|
|
Index sites running Elasticsearch faster
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/cli.rst:106
|
|
22.
|
|
|
**Prerequisite**: Elasticsearch is installed and set up to run on the site.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/cli.rst:109
|
|
23.
|
|
|
When a large site is indexed or re-indexed so that Elasticsearch can display results, this process can take a very long time because the indexing happens on cron runs. If the batch that was indexed finished before the end of the cron though, there is a lag between the next batch starting up again. The ``fast_index`` CLI script starts the next batch indexing right after the previous one finished.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/cli.rst:111
|
|
24.
|
|
|
You run the script with the following command:
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/cli.rst:113
|
|
25.
|
|
|
``sudo -u www-data php admin/cli/fast_index.php``
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/cli.rst:115
|