trying to test my own private repo (working with v3.5.4) I found that it doesn't work and I'm not sure if I'm doing something wrong.
I have a master instance with the Repo App installed. Already I have create a specific login with public access enabled. And I have also uploaded a Test App defining the author and an release. Additionally I have checked the access from the browser with that login and I see the Test App listed in "Public access" section. Maintenance and Builder modes are off.
So far so good.
On the other hand I have started an slave instance, changing in "System" section the Application repository with my params (url, user/pwd, allows, keys... an so on). Maintenance and Builder modes are on.
After that, I visit the "Repository" section in the Admin area but nothing is shown. I have clicked on the reload button and "no results available" message persists. Checking the logs in the master instance shows me that the slave one is asking for the "data/auth" and "data/access" urls but no error is printed anywhere.
I have checked the code trying to find out further and I have found that the "r3/repo/repo_update_modules.go" file (line 24) is trying to load the remote list of modules but I'm not sure if it's doing it properly, since it's asking for 5 attributes from "module" relation but, checking the database schema, these are from "repo_module" relation.
Well, I don't know if this is a clue about what is happening or I misunderstanding the code but any help to configure a private repo is appreciated.