Demo Sites update automatically

As of Aug 24, 2023, the DSpace Demo sites now update automatically

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)

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.

Updating Angular UI Demo (Obsolete)

This procedure is no longer used.  The "ui-demo" branch is unmaintained.

The Angular UI Demo site (https://demo7.dspace.org/) is updated/redeployed automatically when any change is merged into the ui-demo branch of https://github.com/DSpace/dspace-angular

Here's how you update the User Interface Demo:

  1. First, merge any PR(s) that you want to deploy to UI demo
  2. Next, merge/sync those changes over to the ui-demo branch. For example:
    1. git checkout main
    2. git pull
    3. git checkout ui-demo
    4. git merge main
  3. Then, push those changes back up to the ui-demo branch in GitHub
    1. git push upstream ui-demo
  4. 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)
  5. Test it out: https://demo7.dspace.org/

Updating REST API Demo (Obsolete)

This procedure is no longer used.  The "rest-demo" branch is unmaintained.

The REST API Demo Site (https://api7.dspace.org/server/) is updated/redeployed automatically when a change is merged into the rest-demo branch of https://github.com/DSpace/DSpace

Here's how you update the REST API Demo:

  1. First, merge any PR(s) that you want to deploy to REST API demo
  2. Next, merge/sync those changes over to the rest-demo branch. For example:
    1. git checkout main
    2. git pull
    3. git checkout rest-demo
    4. git merge main
  3. Then, push those changes back up to the rest-demo branch in GitHub
    1. git push upstream rest-demo
  4. 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)
  5. Wait for about 5 minutes, and Jenkins will report deployment success/failure on the #rest-api channel in Slack
  6. Assuming Jenkins reported success, the demo REST API should be updated! Test it out: https://api7.dspace.org/server/