Skip to content

Latest commit

 

History

History
168 lines (131 loc) · 5.38 KB

README.md

File metadata and controls

168 lines (131 loc) · 5.38 KB
Raw

gun Build Status

Getting Started

If you do not have node or npm, read this first. Then in your terminal, run:

npm install gun

Now you can require it in the app you want to build.

var Gun = require('gun');

Once included, initialize a gun instance with a file path or your AWS S3 credentials.

var gun = Gun({
	file: 'data.json',
	s3: { // Optional!
		key: '', // AWS Access Key
		secret: '', // AWS Secret Token
		bucket: '' // The bucket you want to save into
	}
});

These are the default persistence layers, they are modular and can be replaced others.

Using S3 is recommended for deployment, and using a file is recommended for local development.

Now you can save your first object, and create a reference to it.

gun.set({ hello: 'world' }).key('my/first/data');

Altogether, try it with the node hello world web server which will reply with your data.

var Gun = require('gun');
var gun = Gun({ file: 'data.json' });
gun.set({ hello: 'world' }).key('my/first/data');

var http = require('http');
http.createServer(function(req, res){
	gun.load('my/first/data', function(err, data){
		res.writeHead(200, {'Content-Type': 'application/json'});
		res.end(JSON.stringify(data));
	});
}).listen(1337, '127.0.0.1');
console.log('Server running at http://127.0.0.1:1337/');

Fire up your browser and hit that URL - you'll see your data, plus some gun specific metadata.

Examples

Try out some online examples or run them yourself with the following command:

git clone http://github.com/amark/gun
cd gun/examples && npm install
node express.js 8080

Then visit http://localhost:8080 in your browser.

API

Below is a really basic overview of how the gun API works. For a more detailed explanation with many more examples, check out the wiki.

Setting Data

In gun, it can be helpful to think of everything as field/value pairs. For example, let's say we have a user object that looks like this:

{
  "username": "marknadal",
  "name": "Mark Nadal",
  "email": "[email protected]"
}

Now, we want to save this object to a key called usernames/marknadal. We can do that like this:

gun.set({
  username: "marknadal",
  name: "Mark Nadal",
  email: "[email protected]"
}).key('usernames/marknadal');

We can also pass set a callback that can be used to handle errors:

gun.set({
  username: "marknadal",
  name: "Mark Nadal",
  email: "[email protected]"
}, function(err){
  // Do something to handle the error
}).key('usernames/marknadal');

Getting Data

Once we have some data stored in gun, we need a way to get them out again. Retrieving the data that we just stored would look like this:

gun.load('usernames/marknadal').get(function(user){
  console.log(user.name); // Prints `Mark Nadal` to the console
});

Basically, this tells gun to check usernames/marknadal, and then return the object it finds associated with it. For more information, including how to save relational or document based data, check out the wiki.

YOU

We're just getting started, so join us! Being lonely is never any fun, especially when programming. I want to help you, because my goal is for GUN to be the easiest database ever. That means if you ever get stuck on something for longer than 5 minutes, you should talk to me so I can help you solve it. Your input will then help me improve gun. We are also really open to contributions! GUN is easy to extend and customize:

Gun.on('opt').event(function(gun, opt){ /* Your module here! */ })

It is also important to us that your database is not a magical black box. So often our questions get dismissed with "its complicated hard low level stuff, let the experts handle it." And we do not think that attitude will generate any progress for people. Instead, we want to make everyone an expert by actually getting really good at explaining the concepts. So join our community, in the quest of learning cool things and helping yourself and others build awesome technology.

Ahead

  • Realtime push to the browser
  • Persistence in the browser
  • Authorization callbacks
  • Security or ACLs
  • Schema Validation
  • Point of Entry Encryption
  • Graph manipulation
  • Server to server communication
  • Test more
  • WebRTC Transport
  • LRU or some Expiry (so RAM doesn't asplode)
  • Bug fixes
  • Data Structures:
  • Groups
  • Linked Lists
  • Collections (hybrid: linked-groups/paginated-lists)
  • CRDTs
  • OT
  • Locking / Strong Consistency (sacrifices Availability)
  • Query:
  • SQL
  • MongoDB Query Documents
  • Neo4j Cypher
  • LINQ
  • Gremlin Query Language