@@ -59,7 +59,7 @@ There are 2 `docker-compose` files provided in the repository, which build the c
* Hyrax processes long-running or particularly slow work in background jobs to speed up the web request/response cycle. When a user submits a file through a work (using the web or an import task), there a number of background jobs that are run, initilated by the hyrax actor stack, as explained [here](https://samvera.github.io/what-happens-deposit-2.0.html).
You can monitor the background workers using the materials data repository service at http://web:3000/sidekiq when logged in as an admin user.
You can monitor the background workers using the RDMS service at http://web:3000/sidekiq when logged in as an admin user.
### Container volumes
The data for the application is stored in docker named volumes as specified by the compose files. These are:
...
...
@@ -140,7 +140,7 @@ The services that you would need to monitor the logs for are docker mainly web a
* fcrepo container will run the fedora service, which will be available in port 8080 at http://localhost:8080/fcrepo/rest
* Solr container will run the Solr service, which will be available in port 8983 at http://localhost:8983/solr
* The web container runs the materials data repository service, which will be available in port 3000 at http://localhost:3000
* The web container runs the RDMS service, which will be available in port 3000 at http://localhost:3000
### Using RDMS
...
...
@@ -155,6 +155,8 @@ You could stop the container using `hd stop`.
This will just stop all of the running containers created by `hd up`
Any background jobs running in the workers container and not having completed will fail, and will be re-tried when the container is restarted.
### To deploy an update of the code
similar to the steps described above, to deploy an update of the code
...
...
@@ -250,7 +252,7 @@ If you would like to create users during startup,
**Note**: The file `hyrax/seed/setup.json` needs to exist before running docker build, for users to be created at start-up.
