Page History
...
- First, install the necessary prerequisites: Docker and Git
- On Windows 10:
- Install Docker Desktop for Windows
- Install Git Bash & verify the installation by running "
git version
" from Command Prompt or Powershell
- On Mac OS:
- Install Docker Desktop for Mac
- Git may already be installed. Run "
git version
" from your terminal to see if it's available. If Git is not yet installed, you will be prompted to install developer tools. If that approach doesn't work, Git may also be downloaded.
- On Linux:
- Install Docker Engine for your Linux OS
- Git may already be installed. Run "
git version
" to check for it. If it is not installed, install Git using your package manager (e.g.sudo apt-get install git
)
- On Windows 10:
- Next, using Git, download (clone) the DSpace Angular UI codebase & move into that codebase directory
Code Block # Download the UI codebase git clone https://github.com/DSpace/dspace-angular.git # Move into the created codebase directory cd dspace-angular # Switch to the 7.x maintenance branch (latest 7.x code) git checkout dspace-7_x
- Using the Docker instructions in that codebase, start up both the DSpace 7 REST API and Angular UI via Docker
First, pull down the latest version of the Docker images (both frontend and backend):
Code Block docker- compose -f docker/docker-compose.yml -f docker/docker-compose-rest.yml pull
Optionally, you can choose to locally rebuild the Angular UI (This is only needed, if you want to try out local changes/customizations to that Angular UI. Otherwise, if you just want to run the default Angular UI, you can skip this step entirely.):
Code Block docker- compose -f docker/docker-compose.yml build
Finally, start up both the Angular UI and REST API via Docker:
Code Block docker- compose -p d7 -f docker/docker-compose.yml -f docker/docker-compose-rest.yml up -d
If you'd like to monitor the startup process, you can "tail" the logs using "logs -f":
Code Block docker- compose -p d7 -f docker/docker-compose.yml -f docker/docker-compose-rest.yml logs -f
- If anything goes wrong, occasionally a simple restart of the images will resolve it. Just do a "down" followed by an "up -d" again:
Code Block # Shut down everything docker- compose -p d7 -f docker/docker-compose.yml -f docker/docker-compose-rest.yml down # Restart everything docker- compose -p d7 -f docker/docker-compose.yml -f docker/docker-compose-rest.yml up -d
- At this point, you should be able to see a completely empty DSpace 7 site. You may now choose to either add test/demo content (see step #5 below) and/or add an initial Administrator account (see step #6 below).
- User Interface: http://localhost:4000/
- REST API: http://localhost:8080/server/
- Next, optionally, you can add test data to your Docker instance. We have two sets of test data available depending on what you want to test out. CHOOSE ONE.
[Option #1: Use AIP test data] We have a set of AIP (Archival Information Package) data which was exported from a DSpace 6.x instance. This test data is good to get a quick feel for the changes in DSpace 7 compared to DSpace 6. It's also the easiest to quickly import as we have an ingest script written for Docker using the "dspace-cli" container. Just run:
Code Block # If you don't have an Admin created with the email "test@test.edu", create it. The AIP ingest runs as that user by default. docker- compose -p d7 -f docker/cli.yml run --rm dspace-cli create-administrator -e test@test.edu -f admin -l user -p admin -c en # This second command will import a batch of test/sample AIPs (see "cli.ingest.yml" for more info) docker- compose -p d7 -f docker/cli.yml -f ./docker/cli.ingest.yml run --rm dspace-cli
- [Option #2: Use a database dump of Entities test data] Alternatively, if you'd like to instead test the new Configurable Entities features, we have a separate database dump which provides Entity test data. (This test data is not yet available in AIP format). Here's how you'd switch your Docker instance to using the Configurable Entities test data
First, you unfortunately need to completely shut down any running volumes and remove them. We will be replacing them with a database dump of Entity test data.
Code Block # Shut down the running containers docker- compose -p d7 -f docker/docker-compose.yml -f docker/docker-compose-rest.yml down # Remove ALL existing volumes docker volume rm $(docker volume ls -q) # NOTE: If you don't want to remove all volumes, you can also remove the volumes in two steps # First, list all volumes, and look for any that have a name starting with "d7". There likely will be 4. docker volume ls # Then, delete each volume (by name) one by one. docker volume rm [volume-name]
Now, let's recreate those containers with the Configurable Entities test data included:
Code Block # NOTE: the `db.entities.yml` here will startup a database image with Entities test data included (from a database dump) docker- compose -p d7 -f docker/docker-compose.yml -f docker/docker-compose-rest.yml -f docker/db.entities.yml up -d # Optionally watch the logs of that command to make sure everything starts back up properly docker- compose -p d7 -f docker/docker-compose.yml -f docker/docker-compose-rest.yml -f docker/db.entities.yml logs -f # Finally, once started, also load up the Entities test "assetstore" (files) & trigger a reindex docker- compose -p d7 -f docker/cli.yml -f docker/cli.assetstore.yml run --rm dspace-cli
Finally, in order to have an initial login, let's create an initial Administrator account using the "dspace-cli" container:
Code Block # This example creates an Admin user with email "test@test.edu" and password "admin". # (You may have already created this user above, before loading AIP test data. If so, you can skip this) docker- compose -p d7 -f docker/cli.yml run --rm dspace-cli create-administrator -e test@test.edu -f admin -l user -p admin -c en
- After a few minutes, you should have a full local installation of DSpace 7 Preview (with test data).
- User Interface: http://localhost:4000/
- REST API: http://localhost:8080/server/
- Admin Login: (whatever login you setup via the "dspace-cli" command above)
- Objects/Pages of interest (within the test data):
- Journal Example represents a journal with journal volumes, issues and articles, as detailed in the Configurable Entities Design.
- Publications Example contains publications which contain a combination of plain-text authors and related author entities. It also contains relations to Research Projects and Organizational Units, as detailed in the Configurable Entities design. Navigating to e.g. a Person will reveal their relations to Publications, Research Projects and Organizational Units.
- Submission/Workflow functionality can be tested using one of the collections in this community where the workflow is enabled. You can use the accounts mentioned above to perform the submission and workflow steps. The admin account can perform the submission and all workflow steps as well.
- Once logged in, MyDSpace functionality is found in the user menu (upper right). Submissions can be started from that page, or via the "New → Item" admin menu (if logged in as an Admin).
Once you are done testing, you can stop Docker and clean up the data (deleting the volumes).
Code Block # Shut down the running containers docker- compose -p d7 -f docker/docker-compose.yml -f docker/docker-compose-rest.yml down # Remove all volumes, images, etc (This removes all the existing data and images) docker system prune --volumes
...