Merge pull request #1098 from sul-dlss/rolling-index-in-dsa

Gemfile

@@ -6,7 +6,6 @@ gem 'bootsnap', '>= 1.1.0', require: false # Reduces boot times through caching;
 gem 'bunny', '~> 2.19' # for rabbitmq
 gem 'committee' # Validates HTTP requests/responses per OpenAPI specification
 gem 'config'
-gem 'daemons' # for rolling indexer
 gem 'dry-monads', '~> 1.3'
 gem 'erubis'
 gem 'faraday'

Gemfile.lock

@@ -128,7 +128,6 @@ GEM
     crack (0.4.5)
       rexml
     crass (1.0.6)
-    daemons (1.4.1)
     date (3.3.4)
     deep_merge (1.2.2)
     deprecation (1.1.0)
@@ -460,7 +459,6 @@ DEPENDENCIES
   capistrano-shared_configs
   committee
   config
-  daemons
   dlss-capistrano
   dor-services-client (~> 14.1)
   dor-workflow-client (~> 7.0)

README.md

@@ -10,29 +10,7 @@ For more information about the fields and their purpose see: https://docs.google
 
 ## Rolling indexer
 
-This helps keep the index fresh by reindexing the oldest data. It is managed as a systemd service. To interact with it from your machine, you can use Capistrano:
-
-```shell
-$ cap ENV rolling_indexer:status
-$ cap ENV rolling_indexer:start
-$ cap ENV rolling_indexer:stop
-$ cap ENV rolling_indexer:restart
-```
-
-Or if you're on a server that has the `rolling_indexer` capistrano role, use systemd commands:
-
-```shell
-$ sudo systemctl status rolling-index
-$ sudo systemctl start rolling-index
-$ sudo systemctl stop rolling-index
-$ sudo systemctl restart rolling-index
-```
-
-**NOTE 1**: The rolling indexer is automatically restarted during deployments.
-
-**NOTE 2**: The rolling indexer runs only on one node per environment. Conventionally, this is the `-a` node.
-
-**NOTE 3**: The rolling indexer logs to `{capistrano_shared_dir}/log/rolling_indexer.log`
+This has been moved to dor-services-app for more efficient access to cocina-models for objects.
 
 ## API