-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Support Unix Sockets #4218
Comments
There is some discussion on unix sockets in ipfs/notes#129. This is probably also blocked by #3856 |
cc @keks this is something we want to be able to do with the ipfs cmds lib |
Yes! That would be rad. I think the best way would be to make a wire format that works directly on top of a reliable transport, so it doesn't matter whether we use unix domain sockets or e.g. websockets (which have been requested in the past). |
Not to add more work to everyone's plates, but unix socket support for go-ipfs would be great, and I would definitely use it in production. |
All the work was client-side. Unix domain socket multiaddrs already worked server-side. fixes #4218
All the work was client-side. Unix domain socket multiaddrs already worked server-side. fixes #4218
All the work was client-side. Unix domain socket multiaddrs already worked server-side. fixes #4218
All the work was client-side. Unix domain socket multiaddrs already worked server-side. fixes #4218
Nice work! |
All the work was client-side. Unix domain socket multiaddrs already worked server-side. fixes ipfs#4218
All the work was client-side. Unix domain socket multiaddrs already worked server-side. fixes ipfs#4218
All the work was client-side. Unix domain socket multiaddrs already worked server-side. fixes ipfs#4218
All the work was client-side. Unix domain socket multiaddrs already worked server-side. fixes ipfs#4218
All the work was client-side. Unix domain socket multiaddrs already worked server-side. fixes ipfs#4218
All the work was client-side. Unix domain socket multiaddrs already worked server-side. fixes ipfs#4218
Version information:
Type:
Feature
Severity:
Low/Medium
Description:
Please consider supporting the option to bind the ipfs/http-gateway and/or the API to a unix socket instead of (or in addition to) a TCP socket.
The text was updated successfully, but these errors were encountered: