This documentation is for Release 7.x and above.
For older releases:
Changes to configuration files often require restarting Avalon to take affect. They also require Resque (the background jobs processor) to be restarted.
Avalon Web Application
|Contents||Environment-specific Avalon configuration options|
name: 'Avalon' # used in page titles
- :name: My LDAP Server
Managing Master Files explains available strategies for how avalon can handle master files after they have been processed.
Bibliographic Import Configuration explains how to configure Avalon to import metadata from an external source such as an OPAC.
Config overwrites should be placed in
|Purpose||Environment-specific database connection information for Rails.|
|Notes||See Configuring a Database in the Ruby on Rails Getting Started Guide for more options. Changing the database adapter will require updating Gemfile to require the correct adapter. Here are the instructions for installing the mysql adapter called mysql2.|
|Contents||Environment-specific Fedora repository connection information for Hydra|
Configuration for optional Intercom feature. Allows this instance on Avalon to push contents to another instance of Avalon.
Intercom utilizes the Ingest API and requires an API token to connect. This token is generated on the target Avalon with `bundle exec rake avalon:token:generate username=archivist email@example.com`
The streaming files will remain in place. Both instances of Avalon must be able to stream from that location.
|Purpose||Environment-specific Solr connection information for Hydra|
|Contents||Role groups and associated members to initialize the Hydra access controls database with|
|Notes||Example environments: development, production, test. So the filename would look like role_map_production.yml for the production environment.|
Rails 4+ uses a secrets.yml file to store a secret key used for signed cookies as well as other things. See http://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html#config-secrets-yml for more information.