Setting up a proxy that isn't a docker container

[TXJustin]

I have godoxy installed on a docker host and have installed the agent on a different docker host and those containers show up and work. I can not seem to get an endpoint that is not a docker container to work.

For my first test attempt, I'm trying to connect through godoxy to the GUI of a proxmox server. Here is what I have entered. . pve.my.domain points to the IP address of the machine running godoxy -- the same Ip address I use successfully for docker containers through Godoxy. My proxmox host is 192.168.5.30. I tried toggling no_tls_verify since proxmox serves that page under a SSL certificate, and makes no difference. I get a 404 error always.

[yusing]

Have you saved the file? Did you see routes reload log?

[TXJustin]

I got it figured out, asking about the reload in the log pointed me in the right direction.. I did not have the pve.yml file as an included file in the route providers screen.

Question - what is the advantage / disadvantage of having all routes in a single file vs. separating out routes into more than one yml? The docs shows examples with logical groupings like LXC containers in one yml, and VPS in another. Is there an advantage to this beyond organization or any limit to the number of routes per file ?

[yusing]

There's no limit to the number of routes per file. You may just put all of them in one.