This tutorial is how to post website/application on IPFS and link with ENS domains(.eth).
- Try it: http://portalnetwork.eth
If you have any question please contact us for help:
This tutorial is how to post website/application on IPFS and link with ENS domains(.eth).
If you have any question please contact us for help:
#!/usr/bin/env bash | |
set -e | |
[ -z "$CLUSTER_SECRET" ] && echo "Need to set CLUSTER_SECRET" && exit 1; | |
echo 'export IPFS_PATH=/data/ipfs' >>~/.bash_profile | |
echo 'export IPFS_CLUSTER_PATH=/data/ipfs-cluster' >>~/.bash_profile | |
source ~/.bash_profile |
IPLD-based Version History
This is just a sketch of a possibility. If we just want a git-style toolchain with git version graph, it might be better to just put an ipfs storage adapter behind go-git -- basically putting IPFS unixfs trees where git usually creates git tree objects. In that case you would have regular git commit objects, not IPLD objects. That would be less reusable beyond the git context but it would fit better with existing git-based tooling.
Keep in mind: it will be really useful to be able to use IPFS files api to manipulate these trees, allowing you to do things like modify part of a large dataset and commit the changes without ever pulling the whole dataset -- you can just pull the parts that you're changing.
This is a guide for aligning images.
See the full Advanced Markdown doc for more tips and tricks
#!/usr/bin/env bash | |
REMOTE_HOST=${1-"YOUR REMOTE HOST HERE"} | |
DEFAULT_API_FILE="$HOME/.ipfs/api" | |
API_FILE="${IPFS_PATH-$DEFAULT_API_FILE}" | |
if [ -e "$API_FILE" ]; then | |
echo "IPFS API is already running" | |
exit 1 | |
fi |
Collection of License badges for your Project's README file.
This list includes the most common open source and open data licenses.
Easily copy and paste the code under the badges into your Markdown files.
Translations: (No guarantee that the translations are up-to-date)