Version information:
root@23b28683cdc7:/# ipfs version --all
go-ipfs version: 0.4.10-
Repo version: 5
System version: amd64/linux
Golang version: go1.8.3
root@23b28683cdc7:/#
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.
cbluth
All 5 comments
There is some discussion on unix sockets in https://github.com/ipfs/notes/issues/129. This is probably also blocked by https://github.com/ipfs/go-ipfs/pull/3856
magik6k
on 7 Sep 2017
cc @keks this is something we want to be able to do with the ipfs cmds lib
whyrusleeping
on 4 Dec 2017
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).
I'm working on getting cmds1.0 out as soon as I can. Afterwards I'll tackle this one.
keks
on 6 Dec 2017
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.
kyledrake
on 19 Oct 2018
Nice work!
teran-mckinney
on 1 Oct 2019
Related issues
magik6k
路
3Comments
whyrusleeping
路
4Comments
jonchoi
路
3Comments
amiyatulu
路
3Comments
daviddias
路
3Comments
Most helpful comment
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.