On the original topic, I think the package registry can only store single files, since it it for packages. Putting the datacite.xml there is already an "extension" of its purpose, I guess (not arguing against it). Everything that involves a folder structure, and cannot be tarballed, needs to be copied to the webserver.
I have not thought of it, makes totally sense. However, then we do not need to store it on the web server or in the GitLab package registry, right? (Right now, we do not even link it in the releases.)
Well, since adding a file to the package registry is only one API request via curl, this is not a FACILE_RS
feature.
For the initial question, I am not sure if we need those assets at all. We archive the code in RADAR anyway. Creating a bag or backpack something we did before the RADAR integration and then we kept it to show that this can be done with FACILE_RS
, I guess. I think nobody would miss the bag.
Same for the docker image. I think its even arguable if that is needed in the radar release, here: https://radar.kit.edu/radar/en/dataset/cvBpGmWbwiwVzLjw# (it 1.3 GB!).
Docker users will get it through the registry, downloading an image and then using it locally is not common (I think). We could skip the whole upload-docker-archive
step here: https://git.opencarp.org/openCARP/openCARP/-/blob/master/.gitlab/ci/docker.gitlab-ci.yml?ref_type=heads#L160
Maybe we should make it optional to use the registy or a ssh connection. (and then use it like you suggested).
Jochen Klar (533726fb) at 28 Feb 16:27
Extend pre-commit-config and run ruff linter