Archived repositories and the living infrastructure

[Giovanni Tirloni]

Hello,

Our infrastructure is evolving and one of the main goals is to run all our applications on containers. For that, the apps/websites need to be "containerized", that is, they must have a Dockerfile and a published image.

While working on containerizing some of our apps, I encountered a few repositories that are archived (read-only):

https://github.com/fluid-project/videoPlayer
https://github.com/GPII/prefsEditors

Although they are archived, they are still served publicly at https://build.fluidproject.org as separate modules/paths.

That creates a dilemma for me because I need to properly integrate them into a CI/CD workflow. They will likely require more changes as new Docker images are released and they need to be updated for security fixes, etc. In other words, no more work is planned on these projects but they are still very much alive in the infrastructure.

I see two paths forward:

  *   They are unarchived so I can submit PRs to have the Dockerfile added (and future changes).
  *   They are copied into the build.fluidproject.org and served as static content from there

Any thoughts?

Regards,
Giovanni Tirloni
DevOps Engineer
Inclusive Design Research Centre, OCAD University
https://idrc.ocadu.ca<https://idrc.ocadu.ca/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20200611/a75144e2/attachment.html>