Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>As @hakre said, Heroku runs apps on an <a href="https://devcenter.heroku.com/articles/dynos#ephemeral-filesystem" rel="nofollow">Ephemeral filesystem</a>. This means your local storage will be lost when the instance restarts.</p> <p>Depending on the data you want to be storing, there are several options to store it.</p> <ol> <li>Cookie: Send it back in a cookie and let the browser take care of it. This is viable if the data is created by the user and it expires at some point.</li> <li>PostgreSQL: If you are using an SQL database in your application, it could go there. Either as a deserialized row or a <code>TEXT</code> field.</li> <li>CDN: If the data is to be public to all, you could upload it to for example Amazon S3 or Rackspace CloudFiles and publish the container. Then you can refer to it by URL.</li> <li>Cloud storage: If the data needs some access control, you can still upload it to S3 or CloudFiles and pull it from there programmatically when it is requested. If there is a performance issue, you could cache it in Memcache or some of the other cache addons.</li> <li>Document database: <code>MondoDB</code> and <code>CouchDB</code> store data as JSON documents. Both have plenty of features. Writing and reading are elementary operations on both. If you need a version history, <code>CouchDB</code> does that for you (it stores all revisions of the JSON by default.</li> <li>Browser local storage: You can store data on the browser now that we have HTML5. It is a bit bleeding edge and will not work on some of the older browsers still around.</li> </ol> <p>There are plenty of other ways of storing your JSON documents on places other than a file. These are just the tip of the iceberg.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload