Contribute to the DSpace Development Fund

The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.

As of August 2023, the and sites are managed/hosted by the DSpaceDirect hosting team within Lyrasis as a donated, in-kind contribution back to the DSpace program.

This page is a guide for how these sites are setup and who to contact for specific needs.  If major issues occur, it is best to contact Tim Donohue or one of the other Lyrasis team members.

General Setup / Info


The and sites are hosted in Amazon Web Services (AWS) using the Docker images created via our Docker build scripts (more info below). 

Both sites are deployed using Terraform modules to AWS Elastic Container Service (ECS)

The code behind these Terraform modules is open-sourced and made available at  It can be used as a guide/example for other similar setups, but these modules are unsupported at this time.  They are built and maintained by the hosting team within Lyrasis specifically for these demo sites.

Docker Images used

The and setups are identical except for the Docker images used by each. uses the Docker Images from the current major release (7.x). uses the Docker Images from the development branch (main).

Updating Docker images

Docker images for DSpace frontends/backends update automatically via GitHub Actions.  Anytime a code change is made to either the "main" or "dspace-7_x" branches, the GitHub Action will trigger.  This results in the image being rebuilt & send to DockerHub

NOTE: each branch uses the version of the GitHub action which exists on its branch.  So, any updates to the GitHub action must be pushed to BOTH branches.

Restarting / Redeploying sites and will automatically redeploy anytime a change is made to their Docker image.  (This is controlled via webhooks installed in our DSpace organization at DockerHub)

For example:

  • If the "latest-dist" image changes for "dspace-angular", then the frontend will redeploy.  (This image will automatically update anytime a new change is pushed to the "main" branch of the "dspace-angular" codebase)
  • If the "dspace-7_x" image changes for "dspace", then the backend will redeploy.  (This image will automatically update anytime a new change is pushed to the "dspace-7_x" branch of the "dspace" codebase.)

Updating site configurations

At this time, all site configurations updates must be sent to Tim Donohue or the Lyrasis team.  All site configurations are currently managed via environment variables which must be configured in the (private) codebase for the demo site. 

The basic environment variable setup can be seen in the Terraform modules codebase here:

Reset site content

At this time, site content (for either site) can only be reset by Tim Donohue or the Lyrasis team.  A command-line script exists to allow site content to be immediately reset to the demo entities data set.  However, at this time it cannot be run externally, so someone at Lyrasis has to login the the instance and run it manually.   

Eventually, we hope to schedule this script to run once per week to ensure site content is reset on a regular schedule.

  • No labels