4 ms·

It seems like almost every project I work on could benefit from a general-purpose library for storing JSON documents along with a change history, including the

It seems like almost every project I work on could benefit from a general-purpose library for storing JSON documents along with a change history, including the change timestamp and author. Also the ability to merge two divergent branches and flag merges that need manual attention. I feel like this has been re-invented again and again. It's a bit like embedding git in your application---and maybe that's even the best way to go. It would sure be useful! So I wonder if this Wiki project will have some way to extract just that bit of functionality. The distributed nature makes me thing probably not, but who knows?

robterrell 12y ago
Check out PouchDB. That's exactly what it's designed for: JSON document storage with remote synchronization capabilities.
- kolev 12y ago
  Isn't that tightly-coupled with CouchDB though?
  - ssutch3 12y ago
    PouchDB uses the CouchDB sync protocol to sync to multiple servers (or other PouchDB databases). PouchDB is also planning on offering a lightweight server-side PouchDB that runs in Node. FWIW any database could potentially implement the CouchDB sync protocol. http://dataprotocols.org/couchdb-replication/ http://dataprotocols.org/couchdb-replication/
    - kolev 12y ago
      Thanks! This would definitely make it vastly more popular!
    - nolanl 12y ago
      There actually is a PouchDB Node server already: https://github.com/pouchdb/pouchdb-server/ https://github.com/pouchdb/pouchdb-server/. Installing it is as easy as `npm install -g pouchdb-server` Also, Drupal recently announced that they're going to offer a CouchDB-compatible server. So yeah, anybody can implement the sync protocol. :) http://wearepropeople.com/blog/a-content-staging-solution-for-drupal-8-and-more http://wearepropeople.com/blog/a-content-staging-solution-fo...
      - kolev 12y ago
        Thanks! How did I miss this?
lgas 12y ago
Camlistore seems like it would serve as a great foundation for something like that (or Ward's federated wiki). It was created with a similar goal in mind (stop writing CMSes over and over) by Brad Fitzpatrick (of LiveJournal/memcached/etc). https://camlistore.org/ https://camlistore.org/

robterrell 12y ago

Check out PouchDB. That's exactly what it's designed for: JSON document storage with remote synchronization capabilities.

kolev 12y ago
Isn't that tightly-coupled with CouchDB though?
- ssutch3 12y ago
  PouchDB uses the CouchDB sync protocol to sync to multiple servers (or other PouchDB databases). PouchDB is also planning on offering a lightweight server-side PouchDB that runs in Node. FWIW any database could potentially implement the CouchDB sync protocol. http://dataprotocols.org/couchdb-replication/ http://dataprotocols.org/couchdb-replication/
  - kolev 12y ago
    Thanks! This would definitely make it vastly more popular!
  - nolanl 12y ago
    There actually is a PouchDB Node server already: https://github.com/pouchdb/pouchdb-server/ https://github.com/pouchdb/pouchdb-server/. Installing it is as easy as `npm install -g pouchdb-server` Also, Drupal recently announced that they're going to offer a CouchDB-compatible server. So yeah, anybody can implement the sync protocol. :) http://wearepropeople.com/blog/a-content-staging-solution-for-drupal-8-and-more http://wearepropeople.com/blog/a-content-staging-solution-fo...
    - kolev 12y ago
      Thanks! How did I miss this?

lgas 12y ago

Camlistore seems like it would serve as a great foundation for something like that (or Ward's federated wiki). It was created with a similar goal in mind (stop writing CMSes over and over) by Brad Fitzpatrick (of LiveJournal/memcached/etc). https://camlistore.org/ https://camlistore.org/