@seanchoqThere is no problem running multiple food computers on one lan, and you could download the UI and run it locally (putting in your food computer’s private ip address).
The trouble is using the OpenAg UI with more than one. That problem does not currently have a solution. The limitation is that the UI assumes you are using port 5984, and there is no way to change parameter in the current code (which is hosted in gitHub).
Personally I think the UI needs some significant overhaul. All of the charting variables are in a control file in gitHub, so they cannot be changed for a customized build. I think the variables should be a table in the local database, which the hosted UI can read (as it does all the data). That way they could be different for each PFC.
Your dynamic IP cannot be stored in the database, but I don’t see why a port number could not be passed to the UI as the IP is. This would not actually require changing the database port on each PFC, it would only require some twiddling with the port forwarding - multiple ‘public’ ports with each being routed to a different internal IP, but all could have the same port number.
I have not seen any discussion on changing the UI code, but I am sure they would be happy if you wanted to give it a go.