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
**NOTE: As of version 2.5.2, the following parameters (oai_repository_name, oai_record_prefix, and oai_admin_email) have been deprecated. They should be set in the Staff User Interface. To set them, select the System menu in the Staff User Interface and then select Manage OAI-PMH Settings. These three settings are at the top of the page in the General Settings section. These settings will be completely removed from the config file when version 2.6.0 is released.**
226
220
227
221
#### `AppConfig[:oai_repository_name]`
@@ -279,46 +273,32 @@ want ArchivesSpace to put its data files elsewhere.
279
273
280
274
#### `AppConfig[:backup_directory]`
281
275
282
-
> TODO - Needs more documentation
276
+
Directory to store automated backups when using the embedded demo database (not mysql). This defaults to `demo_db_backups` within the `data` directory.
The maximum number of distinct facet terms Solr will include in the response for a given field.
309
291
310
292
`AppConfig[:solr_facet_limit] = 100`
311
293
312
294
#### `AppConfig[:default_page_size]`
313
295
314
-
> TODO - Needs more documentation
315
-
296
+
The number of records included in each page in all paginated backend api responses.
316
297
`AppConfig[:default_page_size] = 10`
317
298
318
299
#### `AppConfig[:max_page_size]`
319
300
320
-
> TODO - Needs more documentation
321
-
301
+
Requests to the backend api can define a custom page_size param. This is the maximum allowed page size.
322
302
`AppConfig[:max_page_size] = 250`
323
303
324
304
### Cookie prefix
@@ -332,71 +312,86 @@ Default is "archivesspace".
332
312
333
313
`AppConfig[:cookie_prefix] = "archivesspace"`
334
314
335
-
### Indexer settings
315
+
### SUI Indexer settings
336
316
317
+
The size of each batch of records passed to each indexer worker-thread to process and push to solr.
337
318
The periodic indexer can run using multiple threads to take advantage of
338
319
multiple CPU cores. By setting these two options, you can control how many
339
320
CPU cores are used, and the amount of memory that will be consumed by the
340
321
indexing process (more cores and/or more records per thread means more memory used).
341
-
342
322
#### `AppConfig[:indexer_records_per_thread]`
343
323
324
+
The size of each batch of records passed to each indexer worker-thread to process and push to solr. More records per thread means that more memory will be used by the indexer process.
344
325
`AppConfig[:indexer_records_per_thread] = 25`
345
326
346
327
#### `AppConfig[:indexer_thread_count]`
347
328
329
+
The number of worker-thread to be used by the SUI indexer. More worker-threads means that more CPU cores will be used.
348
330
`AppConfig[:indexer_thread_count] = 4`
349
331
350
332
#### `AppConfig[:indexer_solr_timeout_seconds]`
351
333
352
-
> TODO - Needs more documentation
334
+
The indexer is making requests to solr in order to push updated records to the solr index. This is the maximum number of seconds that the indexer will wait for solr to respond to a request.
353
335
354
336
`AppConfig[:indexer_solr_timeout_seconds] = 300`
355
337
356
338
### PUI Indexer Settings
357
339
358
340
#### `AppConfig[:pui_indexer_enabled]`
359
341
360
-
> TODO - Needs more documentation
361
-
342
+
If false no pui indexer is started. Set to false if not using the PUI at all.
362
343
`AppConfig[:pui_indexer_enabled] = true`
363
344
364
345
#### `AppConfig[:pui_indexing_frequency_seconds]`
365
346
366
-
> TODO - Needs more documentation
367
-
347
+
The number of seconds between each run of the PUI indexer. The indexer will perform and indexing cycle every configured number of seconds.
368
348
`AppConfig[:pui_indexing_frequency_seconds] = 30`
369
349
370
350
#### `AppConfig[:pui_indexer_records_per_thread]`
371
351
372
-
> TODO - Needs more documentation
352
+
The size of each batch of records passed to each indexer worker-thread to process and push to solr.
353
+
The PUI indexer can run using multiple threads to take advantage of
354
+
multiple CPU cores. By setting these two options, you can control how many
355
+
CPU cores are used, and the amount of memory that will be consumed by the
356
+
indexing process (more cores and/or more records per thread means more memory used).
373
357
374
358
`AppConfig[:pui_indexer_records_per_thread] = 25`
375
359
376
360
#### `AppConfig[:pui_indexer_thread_count]`
377
361
378
-
> TODO - Needs more documentation
379
-
362
+
The number of worker-thread to be used by the PUI indexer. More worker-threads means that more CPU cores will be used.
380
363
`AppConfig[:pui_indexer_thread_count] = 1`
381
364
382
365
### Index state
383
366
384
367
#### `AppConfig[:index_state_class]`
385
368
386
-
Set to 'IndexStateS3' for amazon s3
387
-
388
-
> TODO - Needs more documentation
369
+
The indexer needs a place to store it's state (keep track of which records have already been indexed).
370
+
Set to 'IndexState' (default) to store the state in the local `data` directory.
371
+
Set to 'IndexStateS3' (optional) to store the state in an AWS S3 bucket in the Amazon Cloud.
389
372
390
373
`AppConfig[:index_state_class] = 'IndexState'`
391
374
392
-
#### `AppConfig[:index_state_s3]`
375
+
#### `AppConfig[:index_state_s3]` - Relevant only when using S3 storage for the indexer state
393
376
394
-
Store indexer state in amazon s3 (optional)
395
-
NOTE: s3 charges for read / update requests and the pui indexer is continually
396
-
writing to state files so you may want to increase pui_indexing_frequency_seconds
377
+
If using S3 storage for the indexer state in amazon s3 (optional), you need to configure the access to S3.
397
378
398
-
> TODO - Needs more documentation
379
+
NOTE: S3 charges for read / update requests and the pui indexer is continually
380
+
writing to state files so you may want to increase `pui_indexing_frequency_seconds` and `solr_indexing_frequency_seconds`
381
+
382
+
##### Default configuration using environment variables
383
+
384
+
By default, the S3 configuration is fetched from the following shell environment variables:
385
+
- AWS_REGION
386
+
- AWS_ACCESS_KEY_ID
387
+
- AWS_SECRET_ACCESS_KEY
388
+
- AWS_ASPACE_BUCKET
389
+
390
+
It is using the `:cookie_prefix` configuration as a prefix for the state files stored in the bucket - usefull when using the same bucket to store indexer state of multiple archivesspace instances.
391
+
392
+
##### Configuring S3 access directly in the `config.rb` file
399
393
394
+
TODO
400
395
```ruby
401
396
AppConfig[:index_state_s3] = {
402
397
region:ENV.fetch("AWS_REGION"),
@@ -463,6 +458,12 @@ Proxy URL for the public interface
0 commit comments