jsonpool
Version:
A json database for devs
40 lines (36 loc) • 1.9 kB
HTML
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>About</title>
<link rel="shortcut icon" href="/favicon.ico" type="image/x-icon">
<link rel="stylesheet" href="/css/stackedit.min.css" />
</head>
<body class="stackedit">
<div class="stackedit__html"><h1 id="about">About</h1>
<p>JSON-POOL is a secure way to store json data online, using an rest api.<br>
I was inspired by <a href="http://myjson.com">myjson.com</a> to make an online json storage system,<br>
that unlike myjson gave you the ablity to modify/remove any data you have created using auth tokens</p>
<p>There is a production instance running on <a href="https://jsonpool.herokuapp.com">https://jsonpool.herokuapp.com</a><br>
Which you can use all the time.</p>
<h2 id="api">API</h2>
<p>See <a href="api.html">api.html</a></p>
<h2 id="cli">CLI</h2>
<p>It is posible to start an CLI instance by install jsonpool with <code>npm i -g jsonpool</code><br>
and then executing <code>jsonpool</code>. To specify an port you will need to set the <code>PORT</code> env<br>
variable like this <code>$PORT=8080</code>. Rigth now there are two modes <code>fs</code> (filesystem) and <code>db</code><br>
(database). The file system create induvidial files for each pool, where as the database stores it all<br>
in a single json file, which migth be “cleaner” but in the long run if we end up having millions of millions<br>
of pools and then a single file will get very very slow.</p>
<h2 id="news">News</h2>
<p>The editor is now powered by <a href="https://ace.c9.io">ace</a></p>
<h3 id="todo">TODO</h3>
<ul>
<li>[x] Replace node-json-db with a seprate file system were the data can be encrypted</li>
<li>[x] Dispose of auth key and instead only leave the hash</li>
<li>[x] Replace jsoneditor with something else</li>
</ul>
</div>
</body>
</html>