What is it?
A small tool that operates in a manner analogous to a traditional static http file server. The core motivation is having a static file hosting metaphor for sysadmins who don't want to / need to grok IPFS' model.
It does essentially what “ipfs daemon + ipfs add + ipfs pin” can do, but with a UX analogous to setting up a traditional static HTTP server; this self-contained tool provides a trivial metaphor for simple-web users who want to ensure availability of files.
Advantages
- Small self-contained binary (includes its own IPFS Node)
- Self-contained metaphor -- acts like a traditional http server /wo needing to understand IPFS’ model
- All of the other IPFS niceties (deduplication, cheap LAN replication, free CDN’ing if others on the IPFS network have the files)
hackergrrl
All 5 comments
Could be similar to python -m SimpleHTTPServer, while watch'ing the directory, adding changed files.
> iphost
creating /tmp/ipfs-repo-for-pwd
mounting /path/to/pwd at /ipns/Qmfoobar
iphost listening on http://127.0.0.1:8080
watching /path/to/pwd for changes
ghost
on 2 Apr 2016
And maybe rather call it ipserve? host is a veeery generic term in the context of IPFS.
ghost
on 2 Apr 2016
Yes, agreed 100%. :heart:
hackergrrl
on 2 Apr 2016
Really worth looking into @agentofuser's ipfs-deploy tool https://github.com/agentofuser/ipfs-deploy, I believe it fits this usecase and works extremely well!
daviddias
on 22 May 2019
Additionally, https://fleek.co/ took it to the next level and made website hosting super easy!
daviddias
on 28 Apr 2020
Related issues
mitar
·
3Comments
kevina
·
5Comments
pgte
·
4Comments
czanella
·
3Comments
jbenet
·
4Comments
Most helpful comment
Really worth looking into @agentofuser's ipfs-deploy tool https://github.com/agentofuser/ipfs-deploy, I believe it fits this usecase and works extremely well!