Hi Darryl. By "deploying a CouchDB to an end users computer" you mean the client side? Because if you do, I think you would be interested in PouchDB. You can build a desktop app with Electon (HTML/CSS/JS) and use PouchDB to store local data (offline apps), and later sync them with your CouchDB server.
2016-03-27 21:17 GMT-03:00 Kyle Snavely <[email protected]>: > Hi Darryl, > > I've had really good luck using Python Flask web services supported by a > CouchDB (Cloudant) backend. That will expand your target support from > Windows to most platforms, and might be less overhead if you're talking > about a fairly simple application. I've been down the couch-app route > (successfully) but unless you are talking a very basic application (just > HTML/client-side JS) I've found using an external tool for the web service > to be advantageous. Node would likely provide similar advantages -- > allowing you to break down the problem into a client/server space. > > Cheers, > Kyle > > On Sun, Mar 27, 2016 at 8:10 PM, Darryl Wagoner <[email protected]> wrote: > > > I have been tinkering with CouchDB for about a year and I really like it. > > > > What I have been able to find out the best way to do is deploying a > CouchDB > > to an end users computer. I expect the end users to be fairly dumb. > > During the key times they application will be used, Internet may or may > not > > be available or I would host it on a web hosting service. > > > > The options I have thought about are: > > > > 1. Tell them to install CouchDB and writing a C# web server that runs > the > > SPA. Downside is I limit my customer to windows > > 2. Use CouchDb to server the JavaScript/HTML files. Not a bad solution, > > but I can find any docs on how to do that. It would be great to > repackage > > CouchDb to have my files. > > 3. Have them install Apache or such to server the files > > 4. Have them install another web service ie: nodejs, etc > > > > Suggestions? > > > > thanks > > -darryl > > > -- Joel Wallis Jucá joelwallis.com
