Are you afraid of the API being exposed? The only thing somebody could do is make Cup constantly refresh or see what images you used (to see if you're running any vulnerable versions?). I agree that it isn't a perfect idea to have this publicly exposed but adding authentication would require making Cup stateful (adding a database or something) and besides the large amount of code refactoring, I might need to drop binary release support and only provide container images.

Are you afraid of the API being exposed? The only thing somebody could do is make Cup constantly refresh or see what images you used (to see if you're running any vulnerable versions?). I agree that it isn't a perfect idea to have this publicly exposed but adding authentication would require making Cup stateful (adding a database or something) and besides the large amount of code refactoring, I might need to drop binary release support and only provide container images.

I understood. I will use vpn to restrict access.

Hello! This is by design. Making both servers show each others updates would be too complicated and hard to maintain. I think it's best to have 1 central server and see your server updates from there. It's easier for you too to see everything in one place. You can run the other servers in agent mode instead.

You can run the other servers in agent mode instead.

How to do it?

1st server config:

{
    "servers": {
        "Contabo": "http://100.115.224.118:8000"
    }
}

2nd server has no configuration. Something needs to be added?

You need to add a configuration file like:

{
    "agent": true
}

to the second server.