When building and deploying to a local developer's machine, the copy and ignore rules allow the db/development.sqlite3 file, which is the default database file if no further configuration changes are made, to be copied in from the local directory into the running container. This gets around the issue of not having a properly migrated database in place when the Rails app starts. One benefit of including the developer's database file in the build is that the running Rails app in the container will be identical to the when it is running as a local Rails app because the database will be the same and presumably be pointed to the same Fedora/Solr.
git clone (cd to cloned directory)
bundle exec rake db:migrate
In separate windows, provide Fedora/Solr for the container:
solr_wrapper fcrepo_wrapper Once Fedora/Solr are running, create the AdminSet in the local app directory: bundle exec rails hyrax:default_admin_set:create Now build and run: docker build --tag=essi . docker run --net="host" -p 3000:3000 essi Notes:
A local instance of Redis should also be running on the host machine. If using Docker for Mac, all localhost and 127.0.0.1 references should be replaced with host.docker.internal in config/essi_config.example.yml.
A Samvera Hyrax based image cataloging application. To set up a development environment via Docker:
docker-compose up web. If there is a missing .env.development error, add an empty .env.development file and re-run docker-compose up weblocalhost:3000 or http://essi.docker (if you are using Dory)If using Dory: Dory
sc exec -s solr 'solr-precreate hydra-test /opt/config'For a Hyrax specific guide and setup, please refer to the Hyrax Development Guide at https://github.com/samvera/hyrax/wiki/Hyrax-Development-Guide
Content type
Image
Digest
sha256:f345bb011…
Size
1.4 GB
Last updated
5 days ago
docker pull iublibtech/essi