On 2022-01-18 19:57, Raphael Mejias Dias wrote:
Hello,
I'm trying to setup a reverse proxy on my apache2 server to serve an
another apache2 server running on a vm, basically my root apache2 is
at 192.168.0.15 and my second apache2 is at 192.168.0.15:8280 [1].
My idea is to have 192.168.0.15/zm [2] as 192.168.0.15:8280 [1].
The question is, how to do it?
I've looked up some guides, but it is difficult to setup.
I'm sorry for not answering to the question directly, but why use
apache2?
There are modern alternatives with very simple configuration and low
operational overhead like Caddy (https://caddyserver.com/) where reverse
proxy is just one command: caddy reverse-proxy --to 127.0.0.1:9000
And something completely different like Traefik
(https://doc.traefik.io/traefik/getting-started/quick-start/) which is
geared towards modern cloud native infrastructure with containers and
workload orchestrators like Nomad or Kubernetes.
Usually you don't configure Traefik with static config file, but with
metadata and annotations in K8S and Consul so it is dynamic and
reactive.
Or you can use nginx (which is already considered pretty old and clunky,
but it is much easier than apache still).
