fossil server - bind to interface

(1) By sean (jungleboogie) on 2023-06-23 17:21:53 [source]

Hi,

I would like to have fossil server bind to a specific interface to use a specific IP address, but I don't see an option for that.

Am I overlooking this?

As of now, it will listen on all available ip addresses/interfaces.

Thanks!

(2) By sean (jungleboogie) on 2023-06-23 17:47:20 in reply to 1 [link] [source]

Actually my request is two-fold:

bind to an ip address and to an interface.

(3.1) By Warren Young (wyoung) on 2023-06-24 23:07:34 edited from 3.0 in reply to 2 [link] [source]

I’d use either a reverse proxy¹ or containers’ advanced networking features to achieve this.

EDIT: Telling the OS's network stack to listen on one particular IP is a one-line change to the bind() call, but binding to a specific interface by name is non-portable, outside the BSD sockets API space shared by all common OSes these days. It would be non-trivial to add all of the multiple ways to do this on various OSes to Fossil itself.

^{^} …many of which have IP/interface binding features

(4) By sean (jungleboogie) on 2023-06-25 02:21:51 in reply to 3.1 [link] [source]

Thanks for the research!

I'd like to amend my request to bind to a given IP address and not an interface. :)