> this.emit(doc.key)
Normally this.propName points to the ddoc property, if any. So better
this._emit since properties with _ are prohibited for docs.
ermouth
2015-12-12 16:03 GMT+03:00 Jan Lehnardt <j...@apache.org>:
> I’m in favour of doing something like this.
>
> How
ress you call next(args) when in
CouchDB you just return {path:"...", body:"args"}. Also in node your
middleware can be async, but in CouchDB it should be sync.
ermouth
2015-11-26 5:11 GMT+03:00 Johs Ensby <j...@b2w.com>:
> Ermouth,
>
> > On 25. nov. 2015
> If you could find the time to do a screen recording of what you just
described
https://www.youtube.com/watch?v=_FoI2An3JRc
Bit messy since it‘s impromptu
ermouth
a little and found it very promising.
Since this dirty hack is possible with _list fns only, without js rewrites,
may be someone already employs it? Or at least tried?
ermouth
quot;) this.topology = doc.topology;
All subsequent changes will be processed with updated topology settings,
and we achieved this without touching _replication DB.
Works like a charm.
ermouth
rge branchy docs.
Although we add several more layers here, and they add latency, which
diminish our performance boost. So I‘m not sure if 5x rps and bandwidth per
core achievable, gonna play with it a little.
ermouth
, 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 been using Couch 1.6 with a patch for the rewrite function, but I
> wanted to see how 2.0 in single node mode was d
it.
ermouth
2017-09-15 11:41 GMT+03:00 Harald Kisch <haraldki...@gmail.com>:
> Thank You, ermouth!
> For me this is the best editor for CouchDB and the best way to edit large
> JSON structures.
> It is also the simplest way to install a CouchApp, simply by pasting your
> JSON code i
Thank you, Aurélien!
> and a convincing demo
I appreciate your sense of humor, but I afraid my awful English is not too
convincing )
ermouth
Thank you, Giovanni!
BTW, tested Photon at Smileupps, seems to work. However, I missed one
important detail: if the DB list tab is constantly open and visible, Photon
makes a request every several seconds, polling tasks. Not so good for
pay-for-request services.
Gonna fix it.
Now 100% Futon features coverage. Recorded a screencast about Photon
features https://www.youtube.com/watch?v=MHc6tozNhWU
ermouth
2017-09-08 7:02 GMT+03:00 ermouth <ermo...@gmail.com>:
> Think Photon is ready for more wide testing, https://github.com/
> ermouth/couch-photon
&g
Progress so far: very early public beta
https://github.com/ermouth/couch-photon
About 80% ready I hope, not tested in 2.x at all.
ermouth
2017-08-30 21:45 GMT+03:00 ermouth <ermo...@gmail.com>:
> Work in progress, watch video https://youtu.be/lBVdIPZhDc4 to see current
> state.
&
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
> Opening design documents seems not working
Fixed.
ermouth
ust don‘t have enough details
on mango-related UX. So I‘m asking for hints )
ermouth
Think Photon is ready for more wide testing,
https://github.com/ermouth/couch-photon
As for now, 0.2.830, all original Futon features are covered, except two:
creating sync tasks and view compaction on per ddoc basis.
Most original Futon features were bit improved in Photon. Also Photon
includes
Opening ddocs indeed does not work for some configs (smileupps ie), this
issue will be fixed soon. Encoding _design%2F <=> _design/, you know.
ermouth
2017-09-06 13:24 GMT+03:00 Giovanni Lenzi <g.le...@smileupps.com>:
> Great tool ermouth,
>
> seems very fast and
No CloudWall runtime, it would be too limiting in this particular case.
ermouth
2017-08-24 8:08 GMT+03:00 Johs Ensby <j...@b2w.com>:
> ermouth,
> you are doing this as a cloudwell app with the cloudwall runtime
> supporting the single ddoc app, right?
> Johs
> >
in some way, to make it more rapid and controllable?
ermouth
refully assessed.
Although this trick is acceptable if you postponing upgrade to 1.7.1 for
reasons not under your control, I highly recommend upgrade as soon as
possible.
ermouth
of such complexity using nothing but browser.
ermouth
by any
user except admins.
ermouth
Single-node install without shards.
ermouth
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
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
> "must-fix" issues that is preventing users to upgrade to the latest
> version of CouchDB.
&g
dler/1]).
and
proxy_authentication_handler(Req) ->
couch_httpd_auth:proxy_authentication_handler(Req, chttpd_auth_cache).
But as I can recollect it also finally broke things in some bizzare way.
ermouth
2018-07-05 11:59 GMT+03:00 Johs Ensby :
> >>
> >> Proxy authorization which is also
, however hope it at
least sweetens regrets.
ermouth
issues, and then – long live 1.x.
Unfortunately I’m not subscribed to @dev and can’t reply into past proposal
thread even if get subscribed now.
So if you feel my arguments are reasonable, I ask you to cast ‘-1’ under
that proposal. Thank you.
ermouth
t does not fit for production,
which is well proved by Joan words about paid support requests, github
issues and my own tests.
ermouth
problems were already reported.
ermouth
29 matches
Mail list logo
