I have read the documentation about sites and a local site is exactly what I need.
Use this to expose resources on the same host as your Pangolin server (self-hosted only). No tunnels are created. Required ports must be open on the Pangolin host.
But the following instructions on how to install sites simply does not mention on how to “install” this site.
Yes, I do understand how to create my separate docker networks on the host. I know how to group containers into different networks to only allow access as intended.
I just don’t understand if I still need to install this local site so it shows in my Pangolin dashboard as connected.
Btw. I just forged ahead and managed to access my local resource, but I noticed I can only create a public resource with a local site and no private resource.
You can access the Dashboard and use Pangolin without ever creating a local site.
This is the way i think of it, reverse proxies work by taking in traffic and routing it to a backend. Usually it happens that the backend is a local network that connects to that resource.Modern reverse proxies now use peer to peer connections to remove the idea that the resources has to be on the same network at the proxy.
Now when you create a site, you are telling pangolin hey i have a resource on my local network please route it to the local route.
With that being said local routes is like plugging in a physical network to the reverse proxy to use as well rather that the peer to peer newt.
I don’t use private resources but i will guess it is because the olm client needs direct connection to the private resource. The private resource is only exposed over a service or vm running newt so it can establish that direct peer to peer connection. Local site doesn’t establish that (even though i think it can be through gerbil but i am not too sure)
I thought the local site is just a kind of placeholder, not an actual `newt` client.
In my setup I do have services I want to expose as public resources on the pangolin VPS, but for some reason I have not figured out what to put in as IP/Hostname.
Might just be me, but I have the same issue and tried `127.0.0.1`, `localhost`, `0.0.0.0` but nothing worked.
This was not clear to me reading the documentaion and it is still not clear to me.
Maybe in the future I will be able to expose the service.
Hope this helps a little bit.
The `placeholder` approach at least explains why:
- Private resources
- Health checking
- Docker socket scanning
