Add nginx

[EnoF]

No description provided.

[larskuhtz]

👍 Can you update the README and the ports output in ./network to include these endpoints?

Also, should we stop exporting ports of the EVMs on the host? In that case we would have to fix the hardhat and blockscout configurations to talk to the proxy.

[EnoF]

@larskuhtz I'd recommend to keep exporting the ports for now, as the endpoints are exposed as:

http://localhost:8888/devnet1/ and http://localhost:8888/devnet2/ which is slightly different as usual. As I don't know enough of the dev env/toolings available and if they support a different base url, I'd keep exposing the ports.

[larskuhtz]

I wonder about the URL path names. devnet{1,2} sounds a bit like there are two different networks. What about /chain{0,1}?

In the service API in chainweb-node we actually use /chain/{CHAINID}/....

If we wanted to merge it with the service API of chainweb-node we could use look something like:

/chainweb/0.0/development/chain/{CHAINID}/rpc

With that we would expose all user-facing blockchain HTTP APIs from a single port.

[larskuhtz]

I think, it is also fine to merge this PR as it is and discuss the API design details later in followup PRs.

[larskuhtz]

I think, it would be nice to use a single proxy for the RPCs of the EVMs as well as chainweb-node. In the case the EVM RPCs should probably be exposed at something like

/chainweb/0.0/evm-development/chain/{CHAIN}/rpc

But that can also be done in a followup PR.

[Randynamic]

@EnoF do we still need to keep this PR open?