Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Support Listeners on Unix sockets instead of TCP #69

Open
lukasbindreiter opened this issue Jan 19, 2024 · 0 comments
Open

Comments

@lukasbindreiter
Copy link

Hi,

This is a feature request to make the network="tcp" parameter used here configurable. In our case we would like to use unix as the value here.

Some Background:
I'm using endless in a couple of services and liking it very much 😄
But we are now working on a lite, offline version of our service stack, in which clients connect to a service on the same machine. Here we don't actually need TCP sockets for communication, but can instead use unix sockets directly. Unfortunately I couldn't figure out a way to do this while still using endless.

The Go stdlib supports this out of the box, the only change required was:

listener, err := net.Listen("tcp", "localhost:8080")

to

listener, err := net.Listen("unix", "some-unix-socket.sock")

However, with endless, that part seems to be not configurable.
There seems to be same additional logic for listening on a file already, but only if the ENDLESS_CONTINUE environment variable is set, which then sets isChild to true. I didn't want to mess around in that direction to much.

Is there any chance something like this could be added to endless?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant