A tutorial showing how to reimplement GIT in JavaScript, in order to shed light on the inner workings of GIT.
.github | ||
Blob.js | ||
codemirror-5.60.0 | ||
FileSaver.js | ||
JSZip | ||
pako | ||
sha1.js | ||
Viz.js | ||
.gitignore | ||
.ipfsignore | ||
.nojekyll | ||
build-and-update.sh | ||
CNAME | ||
deploy.sh | ||
directory_hashes.js | ||
favicon.ico | ||
favicon.svg | ||
flake.lock | ||
flake.nix | ||
git-tutorial.css | ||
git-tutorial.js | ||
index.html | ||
ipfs-add.sh | ||
micro_ipfs.js | ||
README | ||
sha256.js | ||
sitemap.html |
CodeMirror: https://codemirror.net/ license MIT sha1.js: https://www.movable-type.co.uk/scripts/sha1.html license MIT pako 2.0.3: https://github.com/nodeca/pako license (MIT AND Zlib) Viz.js v2.1.2: https://github.com/mdaines/viz.js license MIT FileSaver.js: https://github.com/eligrey/FileSaver.js license MIT Blob.js: https://github.com/eligrey/Blob.js license MIT license JSZip v1.8.2: https://github.com/Stuk/jszip/tree/v2.6.1 license (MIT OR GPLv3) GitHub depoloyment environment variables: * IPFS_REMOTE_API_ENDPOINT: one per line * IPFS_REMOTE_TOKEN: one per line (same order as IPFS_REMOTE_API_ENDPOINT) * IPFS_SWARM_CONNECT_TO: multiaddr of peers to connect to, to help as intermediaries when connecting to the DHT & pinning services (can be multiaddr of the pinning node itself if known)