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