rivet
rivet copied to clipboard
rivet-gg
Improve public IP requirement
Currently, bringing up Rivet will encode your public IP into the namespace config. This prevents certain containers from being brought up, since they'll try to be reached through a public IP, and fail.
A solution to allow the cluster to be brought up is to change the public_ip to 127.0.0.1 manually. This also doesn't let the full cluster work. Documentation for this could help, or adding a command to bolt to specify that it should set up on localhost.
However, I think there are still issues when it comes to running just on localhost, as you won't be able to use the hub after it starts. @nathan can you elaborate on the issues of using localhost?
![linear[bot] avatar](https://avatars.githubusercontent.com/in/20150?v=4 "Published by a pub.dev verified publisher"){kind=small}
@forest setting up game servers require use of the public ip to connect the tunnel, so pools can't be created with localhost. dns also requires a public ip (obviously). we can add a validation step to the config saying that you need a public ip to run game servers.
we probably can remove the public ip logic and replace it with just 127.0.0.1. this ties back to removing the auto-generated configs and replacing it with a static config (and just auto-generating secrets).
