what is appropriate branch to test ? does 1.3 or master have cors
merged in ? we could not get earlier cors branch to build due to spider
monkey depend - running on debian testing
On 11/29/2012 04:05 AM, Robert Newson (JIRA) wrote:
[
https://issues.apache.org/jira/browse/COUCHDB-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506395#comment-13506395
]
Robert Newson commented on COUCHDB-1593:
this feels rushed - not a good thing with an enterprise thing like a db
- does couch have big users that need the as is 1.3 features asap or
even sponsors that are wanting to ship every 3 mos regardless ? If not,
why not wait and rally troops to make sure cors features are set,
documentation i
On 11/12/2012 03:36 PM, Randall Leeds wrote:
./configure --enable-js-trunk
thks
on debian testing i386 configure runs okay
but make breaks
couch_js/util.c: In function ‘couch_print’:
couch_js/util.c:216:33: error: invalid operands to binary == (have
‘jsval’ and ‘jsval’)
make[4]: *** [couchjs-
On 11/12/2012 10:59 AM, Dave Cottlehuber wrote:
On 12 November 2012 00:06, john.tiger wrote:
removed the xulrunner stuff - ran configure with libmozjs (as per wiki) -
still same newer version error - this is on Debian Testing
amd64? i386?
i386 but hopefully w/ Debian it shouldn't m
On 11/11/2012 02:33 PM, Dave Cottlehuber wrote:
On 11 November 2012 21:36, john.tiger wrote:
just went to compile on another debian testing machine
I'm getting that spider monkey version is too new ? xulrunner-devel-10.0
that same version formerly compiled the stable couchdb package.
just went to compile on another debian testing machine
I'm getting that spider monkey version is too new ? xulrunner-devel-10.0
that same version formerly compiled the stable couchdb package. maybe
something else is at play here ?
since we're fairly close (by western US standards) and I've been
formulating a presentation on how I believe that the right stack for
modern mobile apps is not mvc but html5, css3, jquery, REST based db - I
will submit this before Sunday
meanwhile need to continue working on implementing and
On 11/07/2012 08:34 AM, Benoit Chesneau wrote:
useful reminder. thanks!
Any topic in view?
cors testing - maybe others have results to discuss, sorry we're so slow
on this - got the branch built and running - within hours should be
trying it out with calls - where are we on go - no go deadline
building from source is always a good refresher in using the
documentation - in my case, it meant going to the web site. Er, sorry,
the web site really sucks, really bad. Cant' find anything. The one
page idea is actually nice but the content is totally useless.
But I did manage to find the
ni files are etc/couchdb/default_dev.ini & local_dev.ini
Cheers
Jan
--
On Sun, Nov 4, 2012 at 11:09 AM, john.tiger wrote:
On 11/04/2012 08:19 AM, Benoit Chesneau wrote:
On Sun, Nov 4, 2012 at 4:07 PM, john.tiger
wrote:
do not see any cors_enable in either default or local ini - easy eno
On 11/04/2012 08:19 AM, Benoit Chesneau wrote:
On Sun, Nov 4, 2012 at 4:07 PM, john.tiger wrote:
do not see any cors_enable in either default or local ini - easy enough to
add but want to be sure if it should already be in the ini files in this
build or that I don't have the right ini
On 11/04/2012 06:09 AM, Benoit Chesneau wrote:
cors_enable=true is a setting in default or local.ini not a configure argument.
- benoît
On Sun, Nov 4, 2012 at 2:44 AM, john.tiger wrote:
a few questions so far:
1) where does "cors_enable=true get set - tried to do sudo ./conf
On 11/04/2012 06:09 AM, Benoit Chesneau wrote:
cors_enable=true is a setting in default or local.ini not a configure argument.
okay, got it, ignore my reply to Simon - will continue on. we'll test
with the default for all cross domains - then would like to figure out
from your instructions o
On 11/04/2012 01:34 AM, Simon Metson wrote:
Hi John,
we are trying it today - delayed by not realizing we needed to run
autoconf (should be in docs)
It is, in the DEVELOPERS file (which took me a while to notice, too).
okay and with @randall's suggestion ./bootstrap seemed to work okay -
but
a few questions so far:
1) where does "cors_enable=true get set - tried to do sudo ./configure
--cors_enable that didn't work
2) ini file ? is that a windows thing ? - also would be helpful to
have an example of that
3) using autoconf gave the following:
configure.ac:22: error: possibly
On 11/03/2012 12:15 PM, Benoit Chesneau wrote:
bump.
Anyone tried it ?
we are trying it today - delayed by not realizing we needed to run
autoconf (should be in docs)
On 11/01/2012 03:28 AM, Simon Metson wrote:
Haven't run it yet, but the structure looks pretty good.
The key decisions so far seem to be:
- build with grunt
- backbone
- require.js (yes?)
- LESS
And I take no issue with any of those.
Great! Garren has a change to the deployment script (to make
On 10/31/2012 05:52 PM, Benoit Chesneau wrote:
Hello all,
So I finally committed my patch about CORS support following the current
W3C working draft [1]. This patch support simple and preflights requests
for a couchdb node. Configuration can also be done for a specific vhost.
okay, what am I m
On 10/31/2012 06:04 AM, Jan Lehnardt wrote:
Thanks Benoit, this is very useful! :)
On Oct 31, 2012, at 10:25 , Benoit Chesneau wrote:
Just a friendly reminder. We have a couchdb dev meeting on 8PM today
when giving times - please indicate time zone - assume this is same time
as previous ?
2 thoughts:
1) would suggest to base it on erica rather than introduce a nodejs
dependency (though encourage any nodejs based alternatives)
2) some talk on irc yesterday re version number - would strong recommend
that futon.next be versioned in sync with couchdb - I've seen other
projects where
thks for info - not entirely sure how this will integrate with the
upcoming CORS commit but when that appears, we will try to use all of it
in a non-couchapp html5 program - previously we could not get things
running with lots of cross-domain errors, etc. Should make for a good
test and a nice
On 09/27/2012 01:28 PM, Benoit Chesneau wrote:
On Thu, Sep 27, 2012 at 9:07 PM, john.tiger wrote:
On 09/27/2012 12:39 AM, Dave Cottlehuber wrote:
On 27 September 2012 07:07, john.tiger wrote:
maybe it's late, but I cannot figure out the docs build from linux
"make html&quo
On 09/27/2012 12:39 AM, Dave Cottlehuber wrote:
On 27 September 2012 07:07, john.tiger wrote:
maybe it's late, but I cannot figure out the docs build from linux
"make html" did not work, neither did python conf.py - what am i missing ?
Hi John,
Thanks for giving it a go. I&#x
maybe it's late, but I cannot figure out the docs build from linux
"make html" did not work, neither did python conf.py - what am i missing ?
On 09/26/2012 03:02 PM, Dave Cottlehuber wrote:
Hi,
After much hand-wringing& gnashing of teeth, we now have a /docs/
branch in git[1], [2], and availa
On 09/26/2012 03:47 PM, Dave Cottlehuber wrote:
On 26 September 2012 23:44, john.tiger wrote:
okay, thks - now what is plan - if docs go into /couchdb/docs then should
stuff in wiki be ported over ? having both docs and wiki is confusing
unless really clear what goes into what.
My evil plan
okay, thks - now what is plan - if docs go into /couchdb/docs then
should stuff in wiki be ported over ? having both docs and wiki is
confusing unless really clear what goes into what.
On 09/26/2012 03:02 PM, Dave Cottlehuber wrote:
Hi,
After much hand-wringing& gnashing of teeth, we now h
we tried last winter to do a couchapp - gave up after never really
getting it to work - forget kanso - forget the "garden" thing someone
mentioned - they are all too complicated
all we wanted was straight forward design docs to load up (no node, no
python, just vim ...) and real good docs to
uh, poll times are in what time zone ? - guess I've already missed most
of them - mon am is not a good time with work constraints - GMT 0 is a
pretty good time (late Europe, late aft US, early morning Asia (i
think) or something like that - Mon-Thurs - just set a time, those who
can will make
On 09/18/2012 09:25 AM, Jan Lehnardt wrote:
Also, from experience, the best chance to get things moving here is
starting, and showing some work. This usually gets other people
excited and contributing. Like everywhere else :)
thks for fast communication:)
sure, I'm just trying to get us invo
I've tried to get things going on documentation (probably the biggest
reason couchdb is not more popular) - I put an initial outline forward -
then nothing - no response. this is not how to build a successful
contributor community. Certainly not like active great projects like
nodejs, inkscap
@Noah
glad you like the idea of a docs team (it will let the core team
concentrate on the db inner workings)
I propose that we set a couple of menu buttons on the main page - maybe
as a start:
- docs
-- couchdb api docs (or whatever you are working on)
-- definitive guide
--
32 matches
Mail list logo
