Skip to content

Blacklight front-end for Californica

License

Notifications You must be signed in to change notification settings

UCLALibrary/ursus

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

UCLA Library Management - Ursus


Ursus is designed as the public interface for UCLA's digital library content.

Bruin Bear (statue) In 1984 to mark its 50th Anniversary, the UCLA Alumni Association commissioned "Mighty Bruins" and presented the Bruin Bear Statue to the university. The statue is now a campus landmark and a focal point in Westwood Plaza.


Build Status Apache 2.0 License Coverage Status This project is using Percy.io for visual regression testing.


Development

This section gives basic instructions to get Ursus running locally. More extensive developer documentation is maintained in the wiki.

Install and run locally

Ursus is a Blacklight application and only needs Solr and MySQL.

Ursus can run locally in two ways:

  1. Stand alone mode
  2. In conjunction with local instance of Californica

Standalone mode

The file docker-compose-standalone.yml includes a setup with a clone of the ursus-stage and sinai-stage solr indexes, so you do not need to run californica and manually ingest material (in fact, californica should #not# be running to avoid port conflicts.)

1. Clone the repo from GitHub

git clone [email protected]:UCLALibrary/ursus.git

2. Change directories into the repo

cd ursus

3. Set up the databases

docker-compose run web bundle exec rails db:setup

If the above commnad throws folowing error

 docker-compose run web bundle exec rails db:setup
Could not find rails_autolink-1.1.8 in any of the sources
Run `bundle install` to install missing gems.
  • Running this command
docker-compose up --build

** Then run the following command again

docker-compose run web bundle exec rails db:setup

4. Bring up the development environment

** Do this after setting up the databases** - the startup scripts require the database to be ready so that they can set feature flags e.g. for the Sinai UI mode.

docker-compose up

Ursus should now be running

The data you're viewing is coming from a solr instance, preloaded with data from [Californica-test] (https://californica-test.library.ucla.edu), and should not need to be changed in most cases, since Ursus is a discovery interface only. You can view the solr console on port 8983.


Running linters and unit tests

Connect to a shell inside the container with:

docker-compose run web bash

Then run the entire suite, except for the cypress integration test, with:

sh start-ci.sh

You can inspect the start-ci.sh script to see which linters and tests this invokes.

Or individually:

  1. root@ursus:/ursus# bundle exec erblint --lint-all
  2. root@ursus:/ursus# yarn run lint
  3. root@ursus:/ursus# rubocop

Ursus WITH Californica's database

Go to the docker.env file for directions

In the docker.env file

  1. Comment out SOLR_URL=http://solr:8983/solr/ursus

  2. Uncomment this line SOLR_URL=http://host.docker.internal:8983/solr/californica

  3. In your terminal run $docker-compose -f docker-compose-with-californica.yml up

Before deploying

  1. Be sure to comment out SOLR_URL=http://host.docker.internal:8983/solr/californica

  2. And uncomment this line SOLR_URL=http://host.docker.internal:8983/solr/californica

You cannot run docker-compose run web bash in this environment.


Steps to connect to Ursus Maria db

Here's how you can do it using Docker and Docker Compose commands.

Step 1: Access the Database Container

docker-compose exec db bash

Step 2: Log into the MariaDB Database

mysql -u root

Step 3: Check Your Tables

USE ursus_development;

Then, list all tables:

SHOW TABLES;

You can also check the schema of a specific table:

DESCRIBE users;
DESCRIBE searches;

You can run sql queries:

select * from searches;

Exiting the Shell

exit;

Additional Tips

Rails Console: For Rails-specific data inspection or manipulation, you can also use the Rails console. Run docker-compose exec web rails console to access it. This is particularly useful for operations that involve Rails models.


Running Rake tasks

  • To run the Rake task, open a terminal, navigate to the root of your Rails application, and execute:
docker-compose run web bash
rake blacklight:clear_tables
  • Or, if you are using Rails 5.1 or later, you should use the rails command instead:
docker-compose run web bash
rails blacklight:clear_tables

Running the integration tests

First, you will need to install node.js and npm locally.

Then cd into the e2e directory and install the javascript dependencies:

cd e2e
npm install

Next, you can either open the cypress test runner GUI with:

npx cypress open

or run the tests in the command line:

npx cypress run

Visual regression tests

Visual regression testing is done via percy.io. This runs only for pull requests on travis; it will not run locally.

Rebuilding the image

If you need to rebuild the docker image (for example, if packages were added to the Gemfile), run:

  1. docker-compose pull
  2. docker-compose up --build