> > > I have little need for such a thing myself, so I’m just throwing this idea > out there for anyone who thinks it looks like a good itch to scratch. >
I do have a need for this class of use. My thread "Fossil as an app server" (nearly a week ago on this list) is in the same direction. Here's something I made 8/9 years ago - a WYSInWYG wiki on top of Subversion using it's auto-increment feature - https://www.youtube.com/watc h?v=WfjK0Pb6IIM. and GET/PUT (and an application in the middle). It bumped head revision and did nothing for clash detection. I'm not going to breath life into that again. Here's where I'm going more recently - 0. Here's the "seatmap" app I made using CouchDB again - http://paulhammant.com/2015/12/21/angular-and-svg-and-couchdb/. It works with CORS enabled directly from JavaScript to CouchDB - REST-centric PUT/GET of a resource. CouchDB isn't a SCM, but it could be with some enhancements. Prospective users of CouchDB should know it is insecure in ways that security experts roll their eyes - https://blog.couchdb. org/2017/01/24/couchdb-ransom-notes/. 1. http://paulhammant.com/2016/06/26/using-rhodecode-and- angular1-as-an-editor-for-a-config-as-code-system/ - the last incarnation of a thing I'm still chasing. An Angular 'form' - directly saving JSON to HEAD revision of a Subversion or Git or Mercurial repo. Heavy lifting courtesy of Rhodecode, which is probably maintaining working copy for me, somehow. While the class of application (SCM backed apps) is what I'm after, there's no REST involved here. 2. Here's me stretching my skills to make a similar editor for Github as a backing store - http://paulhammant.com/2015/06/07/custom-json-editors-for- github/. Again the right class of application, but no REST involved. 3. Going back in time - I coached a new starter (Logan McGrath) at my old company into making a real config editing thing with Perforce as a backing store - http://loganmcgrath.com/blog/2012/11/16/scm-backed-applica tion-configuration-with-perforce/. We wrote this thing, so we sure as shit knew we were maintaining working copy for the client on the server. Right class of application, no REST involved. 4. A pre-cursor for #3 - http://paulhammant.com/2012/ 08/14/app-config-using-git-and-angular/ - using Git a the backing store My nirvana is Fossil upgraded to allow discrete CRUD operations over HTTPS. I'd prefer REST, but will live with anything that I can perform from JavaScript in a page that was a] served up (with mime types) from the same HTTPS interface, or b] from another site/server and interoperating with Fossil resources via CORS. Towards that #0 is the reference that's relevant for the 'ask' now, and #1-#4 are supporting on the class of application, not the precise mechanism (REST or something close enough). I'm pretty sure it's just a question of time until doc-store and VCS convergence happens. As I blog around this topic area, http://paulhammant.com/2012/11/20/very-small-data/ might be interesting too, - Paul
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
