Re: CouchApp build tools

Hi all, Thanks Alexander for your proposal and this mailing list. I am 100% with you in this! Before Smileupps and Couchappy, when we first started developing couchapps, we find it very difficult to understand what a couchapp really was. There was too much confusion about it. The naming of the cou

Re: CouchApp build tools

P.S. I only forgot to mention that we have the luck that couchdb is one of the few db/app server with a native HTTP API . Doesn't an in-browser IDE feel like the natural choice for its couchapp development and deployment environment? --Giovanni 2015-11-09 12:25 GMT+01:00 Giovanni Lenzi :

Re: [PROPOSAL] Speed up _list and _update optimizing req object

Hi ermouth, thanks for these interesting questions >> * .info object generation steals 1-2ms even on very powerful machines the only attribute we used so far was the db_name. Is db_name generation slow too? We never used other parameters included in .info. I can only imagine they may be useful

Re: [PROPOSAL] Speed up _list and _update optimizing req object

Hi Alexander, No, slow is gathering all the stats. Especially in cluster. The > db_name you can get from req.userCtx without problem. > Does req.userCtx contain also db_name currently? I thought it was only for user data (username and roles). Are you saying that it would be possible to gather db

Re: [PROPOSAL] Speed up _list and _update optimizing req object

n : > On Fri, Nov 13, 2015 at 1:28 PM, Giovanni Lenzi > wrote: > >> No, slow is gathering all the stats. Especially in cluster. The > >> db_name you can get from req.userCtx without problem. > >> > > > > Does req.userCtx contain also db_name currently?

Re: [PROPOSAL] Speed up _list and _update optimizing req object

> Every nodeX will have the same "notification" process, which is listening to dbX/_changes. sorry with "same" here, I mean same type of process, but obviously one instance of it, running on each node --Giovanni 2015-11-13 13:00 GMT+01:00 Giovanni Lenzi : > not s

Re: Simple Things

Hi Benjamin, thanks for this interesting idea for a collection of simple things!! This thread could eventually be the starting point to some ad-hoc webpage on the new couchapp.org website, or whatever it will be. Probably some of them may be even useful for future ddoc.me development. To give mor

Re: [PROPOSAL] Speed up _list and _update optimizing req object

eparately by a single or > multiple workers, but use another single db that tracks workers tasks > per db and helps to avoid duplicates tasks since all your dbs are in > sync. > -- > ,,,^..^,,, > > > On Fri, Nov 13, 2015 at 3:03 PM, Giovanni Lenzi > wrote: > >&

Re: "Couch-served app" vs. couchapp

Hi William, the starting error has been naming the python/node.js/ruby/etc. tools with the word couchapp! A tool is not an app,in the sense intended today. Most of the tools are indeed suffixed with the word 'xyz client' or 'xyx tool' just to say to the user: 'hey this tool will be useful for xyz'

Re: serving html pages built from multiple lists or shows

Hi Robin and Nick, You definitely CAN output full html, non js, SEO optimized web pages. We use that for our store index and apps pages (on https://www.smileupps.com/store). We needed to: 1. create html templates of your pages with a templating library(we used handlebars.js), 2. precompile these t

Re: [PROPOSAL] Chainable requests

Wow, very useful!!! It would be finally possible to aggregate multiple document updates on the server-side, thus implementing server-side actions in a secure and complete way, calling a single application api method. I also like the two new ways of priting output: chunked and reduced. Would it be

Re: [PROPOSAL] Chainable requests

d hops completely executed, or the chain will be interrupted? -- Giovanni > > 2015-12-01 16:17 GMT+03:00 Giovanni Lenzi : > > > Wow, very useful!!! > > > > It would be finally possible to aggregate multiple document updates on > the > > server-side, thus i

Re: [PROPOSAL] Chainable requests

connection. But even in this case > I‘m not sure chain must stop. > > Your considerations? > > ermouth > > 2015-12-03 12:25 GMT+03:00 Giovanni Lenzi : > > > 2015-12-01 18:04 GMT+01:00 ermouth : > > > > > Off: I like your new logo (your avatar?) very much

Re: Couchapp experience in 2016

Great job ermouth, you are always on the front line on pushing couchapp borders! JS rewrites seems to really enable them to any kind of use. Performance may be a limit if you are really interested to squeeze each available cpu cycle, ok but, from a business perspective, how does it cost to rea

Re: Fauxton, Futon and licensing obstacles

Great tool ermouth, seems very fast and tabs greatly simplify administration tasks. Opening design documents seems not working... Are you planning to include different editor for them? Thanks for work and great idea! --Giovanni 2017-09-06 8:40 GMT+02:00 Johs. E : > Congratulations with fantast

Re: Photon, 90% progress

WOooOoW, impressive work here. Boosts productivity under every aspect. Photon is hands down the best existing administration experience for couchdb. It's time to happily saying thanks and goodbye to futon/fauxton ;-) Focused and right to the point in no time, thanks for your great work ermouth,