The project's main branch provides a template Spotlight application with SUL branding and functionality.
Exhibits need to provide the following configuration files:
config/database.yml- Standard Rails database configurationconfig/honeybadger.yml- Honeybadger.io exception reporting configurationconfig/blacklight.yml- Blacklight solr configuration- config/initializers/secret_token.rb - Rails secret token
- Redis (for running background jobs with Sidekiq)
See projectblacklight/spotlight for additional requirements.
Install dependencies, set up the databases and run migrations:
$ bundle
$ yarn install
$ bin/rake db:setupSet up an admin user. You will be prompted to enter an email.
rake spotlight:initialize
You can spin up the Rails server using this command. Use the same email created as an admin above.
$ REMOTE_USER="[email protected]" bin/devWhen prompted to create an admin user, the email should match the email provided in REMOTE_USER. This will allow you to bypass authentication.
Create an exhibit while logged in as an admin user in order to navigate and search content.
$ bin/rake spotlight:seed$ bin/rake spotlight:reindexRun RuboCop and tests:
$ bin/rakeIf you'd like to run a single test, you must seed the index first:
bin/rails spotlight:seedTip: if you receive the error message ERROR: Core 'blacklight-core' already exists! you have an instance of Solr running elsewhere. Clean out your data with solr_wrapper clean or search for rogue instances with ps aux | grep solr.
You must be on VPN to deploy the worker machine. Then deploy as usual using Capistrano:
$ cap stage deploy