2 is probably your best option. Just use attachments. /db/doc/index.html

better yet, if possible: host the static files for the SPA yourself, use
the HTML appcache so the files will be avaliable for the users even when
offline, then let the users input their own CouchDB URL/passwords in the
app. store all this relevant data client-side, on localStorage, and let
this hosted SPA connect to their local CouchDBs.

On Sun, Mar 27, 2016 at 9:17 PM, Kyle Snavely <[email protected]> wrote:

> 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
> >
>

Reply via email to