Search Results for ".bin"

A tool for checking the accessibility of your data by IPFS peers. go build will build the server binary in your local directory. go install will build and install the server binary in your global Go binary directory (e.g. ~/go/bin) There are web assets in the web that interact with the Go HTTP server that can be deployed however you deploy web assets. Maybe just deploy it on IPFS and reference it with DNSLink. For anything other than local testing you're going to want to have a proxy to give you HTTPS support on the Go server.

...Download a compatible binary for your system. For convenience, place slack-term in a directory where you can access it from the command line. Usually this is /usr/local/bin. If you want, you can also get slack-term via Go. You can also run it with docker, make sure you have a valid config file on your host system. In addition to running slack-term from the command line by using slack-term, you have some additional flags that you can use. You can specify a different location of the slack term config file. ...

Plugin for presenting an IPFS gateway over i2p. This is only the gateway part, A.K.A. the easy part. It will make your IPFS gateway accessible via i2p clients, but it will not route communication between IPFS nodes over i2p(1). This means that it doesn't make your IPFS instance anonymous, it just makes it accssible to clients anonymously(2). It simply takes advantage of the plugin system to set up some hidden services when the IPFS plugin is initialized. It does this by reading the IPFS...