Page History
Table of Contents |
---|
Demo Sites update automatically
As of Aug 24, 2023, the DSpace Demo sites now update automatically
Info |
---|
A basic summary of the demo sites exists below, but for more details see demo.dspace.org Site |
demo.dspace.org
demo.dspace.org always runs the latest code from the corresponding "dspace-7_x" maintenance branch. It is therefore running the latest 7.x code at all times (NOTE: it updates every time a code change occurs on this maintenance branch, which means it may include unreleased fixes which will be in the next maintenance release)
- https://demo.dspace.org uses the published
dspace-7_x-dist
Docker image built from theDockerfile.dist
on our frontend'sdspace-7_x
branch: https://github.com/DSpace/dspace-angular/blob/dspace-7_x/Dockerfile.dist - https://demo.dspace.org/server/ uses the published
dspace-7_x
Docker image built from theDockerfile
on our backend'sdspace-7_x
branch: https://github.com/DSpace/DSpace/blob/dspace-7_x/Dockerfile - Frontend and backend configuration is managed via environment variables. Contact Tim Donohue or Lyrasis to ask for a configuration change.
sandbox.dspace.org
sandbox.dspace.org always runs the latest code from the corresponding "main" branch. It is therefore running bleeding edge code at all times.
- https://sandbox.dspace.org uses the published
latest-dist
Docker image built from theDockerfile.dist
on our frontend'smain
branch: https://github.com/DSpace/dspace-angular/blob/main/Dockerfile.dist - https://demo.dspace.org/server/ uses the tagged
latest
Docker image built from theDockerfile
on our backend'sdspace-7_x
branch: https://github.com/DSpace/DSpace/blob/main/Dockerfile - Frontend and backend configuration is managed via environment variables. Contact Tim Donohue or Lyrasis to ask for a configuration change.
Updating Angular UI Demo (Obsolete)
Warning |
---|
This procedure is no longer used. The "ui-demo" branch is unmaintained. |
The Angular UI Demo site (https://dspace7-demodemo7.atmiredspace.comorg/) is updated/redeployed automatically when any change is merged into the master
ui-demo
branch of https://github.com/DSpace/dspace-angular
So, shortly after you merge a PR, those changes should appear on the demo site.
Here's how you update the User Interface Demo:
- First, merge any PR(s) that you want to deploy to UI demo
- Next, merge/sync those changes over to the
ui-demo
branch. For example:git checkout main
git pull
git checkout ui-demo
git merge main
- Then, push those changes back up to the
ui-demo
branch in GitHubgit push upstream ui-demo
- At this point, Atmire's server should detect the new changes & redeploy the demo7.dspace.org user interface (NOTE: It may take ___ minutes for the changes to be deployed)
- Test it out: https://demo7.dspace.org/
Updating REST API Demo (Obsolete)
Warning |
---|
This procedure is no longer used. The "rest-demo" branch is unmaintained. |
...
The REST API Demo Site (https://dspace7api7.4sciencedspace.it/dspace-spring-restorg/server/) is updated/redeployed automatically when a change is merged into the rest-demo
branch of https://github.com/DSpace/DSpace(NOTE: We chose to base this demo site off of a separate code branch simply because changes to the REST API can sometimes break Angular UI functionality. So, we don't want newly merged PRs to break the Angular UI demo, and this offers us the opportunity to test the Angular UI against new REST API changes before deploying them to the demo site.)
Here's how you update the REST API Demo:
- First, merge any PR(s) that you want to deploy to REST API demo
- Next, merge/sync those changes over to the
rest-demo
branch. For example:git checkout mastermain
git pull
git checkout rest-demo
git merge mastermain
- Then, push those changes back up to the
rest-demo
branch in GitHubgit push upstream rest-demo
- At this point, 4Science's Jenkins system should detect the new changes. Jenkins will report on the #rest-api channel in Slack that it is redeploying (NOTE: It may take 5 minutes or so for the Jenkin's system to detect the changes and report on Slack)
- Wait for about 5 minutes, and Jenkins will report deployment success/failure on the #rest-api channel in Slack
- Assuming Jenkins reported success, the demo REST API should be updated! Test it out: https://dspace7api7.4sciencedspace.it/dspace-spring-restorg/server/