Hi all.

Please find the attached port of go-ipfs [0].
Also attached is a patch to infrastructure/db/user.list
to reserve a uid/gid for _ipfs.

I'm running an ipfs node at home and pinned a "Hello, OpenBSD!"
file [1] for you :)

DESCR:
IPFS is a global, versioned, peer-to-peer filesystem. It combines good ideas
from Git, BitTorrent, Kademlia, SFS, and the Web. It is like a single
bittorrent swarm, exchanging git objects. IPFS provides an interface as
simple as the HTTP web, but with permanence built in. You can also mount the
world at /ipfs.

Two questions:

1)

The tar.gz provided by upstream contains files at the root without an go-ipfs
folder. I did the following to unpack everything in WRKDIST instead of in
WRKDIR directly. Is there a better approch to do this?

  EXTRACT_ONLY =

  post-extract:
        mkdir -p ${WRKDIST}
        tar xzf "${FULLDISTDIR}/${DISTNAME}${EXTRACT_SUFX}" -C ${WRKDIST}

2)

By default, ipfs creates all files in ~/.ipfs. This can be changed by
specifing IPFS_PATH. Personally I don't like a hidden folder at /var/ipfs/.ipfs
which is why I set IPFS_PATH=/var/ipfs in the rc file.
This requires users of ipfs to always remember to set IPFS_PATH=/var/ipfs

What would you prefer?

2.1) Setting HOME of the _ipfs user to /var/ipfs and have the data
        under /var/ipfs/.ipfs.
2.2) Setting IPFS_PATH=/var/ipfs in the rc file and whenever a user wants to
        interact with ipfs.

Cheers,
Fabian


[0] https://ipfs.io/
[1] https://gateway.ipfs.io/ipfs/Qmb7s5nUsLvCQDsXymui2bSt9imsQBzEVviaJRrhyzeBUD
diff --git a/infrastructure/db/user.list b/infrastructure/db/user.list
index fc8521ab6fd..db8d79c3ab6 100644
--- a/infrastructure/db/user.list
+++ b/infrastructure/db/user.list
@@ -327,3 +327,4 @@ id  user            group           port options
 816                    _libpostal      geo/libpostal
 817 _netshot           _netshot        sysutils/netshot
 818 _vnu               _vnu            www/vnu
+819 _ipfs              _ipfs           net/go-ipfs

Attachment: go-ipfs.tar.gz
Description: Binary data

Reply via email to