We have a production erp server that has heretofore only been accessible from the LAN. We now have a requirement that parts of it be accessible from outside.
We don't run DNS internally, so all access has just been with 192.168.x.x. The few exceptions for accessing from outside the LAN have been done with whitelisting a few IPs in the router's ACL, and adding a static route to forward traffic hitting the router's static WAN IP.
Right now, I've set up a domain name to hit another of our IPs. There is another static route in the router config to forward traffic for that IP to the same server. I've basically just created another way to hit the same server on 80/443.
What I would like to do now is set up a virtualhost config so that traffic coming in via the new domain will hit a particular folder...
domain.com/public for example.
What I'm unsure of, is what, if any, affect this may have on the existing no-virtualhost setup.
If I set up a virtualhost config to point domain-based traffic to a specific folder, do I have to be explicit (set up another virtualhost) about non-domain-based traffic being able to hit the root as it already does now?