That being said, I need to apologize again about this situation. When I archived my repository and promoted your fork instead, the move wasn't very thought-through. The reason for it was that I was tired of maintaining this repository in a personal capacity, and was sad to discover that Paul had made this fork without trying to contribute his Dockerization and documentation improvements to my repository. I should have reached out to him, asking him if he would consider making a PR for it (maybe he just wasn't so familiar with open source contributions, or didn't feel like his work was good enough to be integrated upstream). By creating this fork, Paul probably didn't have the intention to maintain this code base for the use of other institutions, nor to accept external contributions: it was probably just meant to be internal documentation about your own deployment(s) of the service. So pointing to your repository as the new official home of this project was bound to fail, in my opinion.