Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/remram44/dhstore
A thing that stores stuff
https://github.com/remram44/dhstore
backup content-management decentralized object-storage rust
Last synced: 19 days ago
JSON representation
A thing that stores stuff
- Host: GitHub
- URL: https://github.com/remram44/dhstore
- Owner: remram44
- Created: 2015-06-15T16:25:57.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2020-10-04T02:02:17.000Z (about 4 years ago)
- Last Synced: 2024-10-10T18:41:46.065Z (about 1 month ago)
- Topics: backup, content-management, decentralized, object-storage, rust
- Language: Rust
- Size: 994 KB
- Stars: 8
- Watchers: 5
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
[](https://travis-ci.org/remram44/dhstore/builds)
[](https://ci.appveyor.com/project/remram44/dhstore/history)
[Generated documentation](https://remram44.github.io/dhstore/index.html)
What is this?
=============
This is very early work. I am trying to write a decentralized content management system (think Git, not Wordpress) in the Rust language.
Borrowing ideas from [IPFS](https://ipfs.io/) and [Camlistore](https://camlistore.org/), my objective is to write software that can store and index objects, offering replication, sharing and search over multiple nodes.
Use cases:
* Store your backups in an efficient (de-duplicated) manner, and replicate them to different machines
* Index and tag your photos, allowing for efficient search by tag/date/location
* Ingest your Tweets and social media posts for posterity and easy search
* Wiki-like application with rich-text notes linking forward and back to images, files, emails, ...
* Persistent decentralized archive (archive.org mirror?)
* Backend for all kinds of applications (calendar, website, microblogging)
Data Model
==========
dhstore stores objects (structured, indexable documents) and blobs (bunch of bytes). An object is either a list or a dictionary with string keys, and cannot have nested containers. They can however reference other objects and blobs, allowing to store full JSON-like trees.
Everything is content-addressable (referenced by its hash) much like Git or IPFS. However, special objects called permanode allow for mutability: "claim" objects associate a permanode to a value, and can be authenticated via public-key cryptography.
For example, a permanode might be used to collect snapshots of some directory tree. Claims associate the roots of snapshots to the permanode, and can be searched by date.
Dependencies
------------
