Siri integration with CouchDB 1.7.0

Hi, has anyone any experience with integrating Siri voice control with CouchDB? Since Siri is an interface that Apple is still controlling tightly, the workarounds that I know of are send message send mail enter calendar event/reminder E.g. by entering calendar events, you could via calendar

Re: Meet copy-couch!

> From: Martin Broerse <i...@martinbroerse.com> > Date: Sun, Nov 15, 2015 at 8:28 AM > Subject: Re: Meet copy-couch! > To: Johs Ensby <j...@b2w.com> > Cc: couchapp@couchdb.apache.org > > > Johs, > > No I was refering to this: > > http

Re: Ecosystem around CouchDB applications

om/@ensby/e39ac4397cea> Johs > On 9. nov. 2015, at 11.19, Johs Ensby <j...@b2w.com> wrote: > > Hi All, > > I have written the followup Applications in CouchDB article > I am afraid this will be a 10+ minute read, I had to establish a vocabulary > to get to wha

Re: serving html pages built from multiple lists or shows

Hi, I have always used Handlebars serverside to do SEO-friendly pages - a list that merges data and templates - the doc type or other field decides what template to work - used nested templates (sub teemplates for "modules" in the page" to assemble pages on the fly - SEO agency of my clients get

Re: Couch on port 80

buying a pile of sheet metal, a few rubber trees, small pile of copper, a pile of sand, and an oil well. :D > On 18. nov. 2015, at 23.18, Alexander Shorin <kxe...@gmail.com> wrote: > > On Thu, Nov 19, 2015 at 1:05 AM, Johs Ensby <j...@b2w.com> wrote: >> Couch-on

Re: Caching results of _list functions

to access cache you just use >> >> var Cache = require ('Cache').Cache; >> >> Now you can use it like Cache.get(key) and Cache.put(key, val) in rewrite >> and list. Your cache will persist between requests until you change ddoc or >> SM crashes. >

Re: Couchapp experience in 2016

Awsome! if couchapps was ever worth pursuing, you made the largest contribution to proving so. johs > On 2. sep. 2016, at 00.00, ermouth wrote: > > Tried out more or less pure couchapp approach in 2016 realities, I mean JS > rewrites and PouchDB. > > Written down a story

Re: CouchDB 2.0 and "Intuitive HTTP/JSON API and designed for Reliability" for couchapps

iew of new query server on Monday, as a > full replacement for lists, shows, rewrites, updates and so on. With SMS, > emails and all missing stuff. So stay tuned. > > ermouth > > 2017-05-23 13:47 GMT+03:00 Johs Ensby <j...@b2w.com>: > >> Hi, >> we have bee

Re: Photon, 90% progress

Hi >>its hidden potential is still nearly untouched, as I see it. amen! Fantastic job, ermouth! johs > On 15 Sep 2017, at 13:20, ermouth wrote: > > Thank you, Harald! > > Actually, it‘s not a couchapp from thin air, Photon was created inside > browser using couchapps.

Re: Fauxton, Futon and licensing obstacles

Great! Can't wait to start using it johs > On 30 Aug 2017, at 20:45, ermouth wrote: > > Work in progress, watch video https://youtu.be/lBVdIPZhDc4 to see current > state. > > Right now codename Photon is a json with footprint well below 1.5Mb. > > ermouth

Re: Fauxton, Futon and licensing obstacles

Hi, I will post issues on github. Will try to use it in a real situation to get a better feel, but post ideas on UI before I get too used to it. (when I started using Cloudwall, I had a hard time getting my head around it, now I am used to it and feel no pain:) This "DB browser" could

Re: Fauxton, Futon and licensing obstacles

Hi, This lauches and works well in both 1.6 and 2.1 a few things dicovered tabs sometimes dont respond to click numeric startkey not allowed codemirror box crops content some times Missed direct access to attachments This looks very promising, concrats! I have opinions on UX, of course, but

Re: Fauxton, Futon and licensing obstacles

ermouth, you are doing this as a cloudwell app with the cloudwall runtime supporting the single ddoc app, right? Johs > On 23 Aug 2017, at 21:56, ermouth wrote: > > Good idea, however I gonna start with CouchDB ) > > I‘ve recordered 5min screencast about JSON editor for CN

Call for "Must-fix" issues

This thread reach out to CouchDB 1.x users to generate a list of "must-fix" issues that is preventing users to upgrade to the latest version of CouchDB. It is in response to Joan's comment below regarding the non-technical proposal to make a project decision to terminate official Apache

Re: Call for "Must-fix" issues

gt; Single-node install without shards. > > Both the /_setup_cluster endpoint and the Mac binaries already set q=1 & n = > 1 on setup. Everyone else can configure it. > > Best > Jan > — > >> >> ermouth >> >> 2018-07-05 10:10 GMT+03:00 Johs

Re: Call for "Must-fix" issues

> > 2018-07-05 11:20 GMT+03:00 ermouth : > >> Proxy authorization which is also in docs, but absent in 2.x. >> >> ermouth >> >> 2018-07-05 10:10 GMT+03:00 Johs Ensby : >> >>> This thread reach out to CouchDB 1.x users to generate a list of &g

Re: Call for "Must-fix" issues

Hi Harald, how about starting a new thread on the topic, incuding dev@ and users@? Compared to the https://db-engines.com/en/ranking_trend/system/CouchDB (auto collected web data) the review service you linked to have a massive amount of reviews from MongoDB people. Your question could motivate

Re: [PROPOSAL] Officially deprecate CouchDB 1.x.

deprecating 1.x. 1.x is a fine piece of software and existing installations > of it will continue to run just fine, but this project is moving on. > > Best > Jan > — > >> On 8. Jul 2018, at 14:59, Johs Ensby wrote: >> >> Thanks Joan, >> >> Your take on t

Re: On 1.x deprecation

Thanks ermouth, I agree with you that the logic behind the proposal could have been clearer. A sunsetting announcement linked to the reliability criteria for 2.x would have been preferable. I value your opinions very much because I understand that you have deployed large systems with CouchDB at

Re: On 1.x deprecation

OK:) > On 6 Jul 2018, at 12:07, ermouth wrote: > >> Approximately how many 1.x nodes to you have in production now? >> What is your estimated total no of users on these? > > Sorry, can’t disclose this kind of info publicly. > > All I can say I have zero nodes with 2.x in prod, despite we

Re: [PROPOSAL] Officially deprecate CouchDB 1.x.

-1 A sunsetting discussion is very welcome, but this proposal is unclear, based on week arguments and a lack of data, and as decision support not the best of proposals. 1) To "table" a propoal for voting is problematic

Re: [PROPOSAL] Officially deprecate CouchDB 1.x.

hing decision with unclear benefit. Also, I think the result of the recent user survey should be published to support the decision making. Johs > On 7 Jul 2018, at 19:18, Joan Touzet wrote: > > Johs Ensby wrote: >> Thanks for this, Joan >> >> You must have put a lot t