Right, that's known, and I'm working on fixing this.

Ah, okay! Last I remember it was suggested to raise an Issue here and I didn't see one when I checked today. Sorry for the noise. :)

https://registry.fedoraproject.org/ - what version of https://github.com/genuinetools/reg it is running?

How to lookup deploy scripts for this domain?

How to inspect the logs for this service?

@abitrolly ,

https://registry.fedoraproject.org/ is a static page served from our proxies, if I am not mistaken. There is a cron job that is generating the static page every 5 min [0].
This how reg-server is deployed [1]

I think currently https://github.com/genuinetools/reg does not support statically generating the tags that's why we have a 404. I also believe @puiterwijk has a working fork that we should try to submit upstream.

[0] - https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/files/reg-server/cron-prod
[1] - https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/tasks/reg-server.yml

I am confused - registry.fedoraproject.org is a static web site, which is populated by reg and it is also a real container registry. That means that web-server configuration for this domain should be a mix of URLs, so maybe reg generates everything correctly, but tag URL is not served from static dir, but given to registry app.

What is the process to lookup all Ansible configuration for certain domain?

Fixed upstream - https://github.com/genuinetools/reg/issues/107#issuecomment-405187849 but now reg-server package doesn't make much sense? How much time it will take to edit package info and release new scripts, because:

1. reg-server is now reg server
2. --once is now -once

once can have two dashes both work :)

@abitrolly ,

We need to update the reg package to the latest upstream, then change the cron job in ansible to use reg instead of reg-server.

We need to update the ansible task also to install reg instead of reg-server

This is finally done.

Sorry for the long delay.

:registered: