From 455003d0e924414db339395e8367166e7820c5da Mon Sep 17 00:00:00 2001 From: Alberto Sartori Date: Mon, 24 Feb 2025 14:16:42 +0100 Subject: just serve: allow clients to access execution endpoint with a different address To properly use `just serve`, both the client and the serve instance must talk to the very same execution endpoint. Typically, both the client and serve can reach out to the execution endpoint via the same IP address. However, it might be possible that the client and a serve instance know the same execution endpoint by means of differnet IP addresses. For example, the client knows the execution endpoint address through an _external_ IP address, while the serve instance, deployed within the same network infrastructure, only knows the _internal_ IP address. This patch adds the subkey `"client address"` -- of the key `"execution endpoint"` -- in the serve configuration file, to specify the alternative pair `address:port` used by the client. --- share/man/just-serve-config.5.md | 3 +++ 1 file changed, 3 insertions(+) (limited to 'share') diff --git a/share/man/just-serve-config.5.md b/share/man/just-serve-config.5.md index a21adf03..f890cd6a 100644 --- a/share/man/just-serve-config.5.md +++ b/share/man/just-serve-config.5.md @@ -82,6 +82,9 @@ The configuration file is given by a JSON object. **`serve`**. For subkey *`"address"`* the value is a string specifying the remote execution address in a NAME:PORT format. + For subkey *`"client address"`* the value is a string specifying + the remote execution address used by the client in a NAME:PORT + format. If not provided, it defaults to *`"address"`*. For subkey *`"compatible"`* the value is a flag which specifies whether the remote endpoint uses the original remote execution protocol. If the key *`"execution endpoint"`* is given, the following three keys will -- cgit v1.2.3