You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "john.tiger" <jo...@gmail.com> on 2012/11/04 02:44:43 UTC
cors branch testing
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 undefined macro: AM_CONFIG_HEADER
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:25: error: possibly undefined macro: AM_INIT_AUTOMAKE
configure.ac:28: error: possibly undefined macro: AC_ENABLE_SHARED
configure.ac:29: error: possibly undefined macro: AC_DISABLE_STATIC
configure.ac:33: error: possibly undefined macro: AC_PROG_LIBTOOL
configure.ac:61: error: possibly undefined macro: AC_DEFINE
configure.ac:207: error: possibly undefined macro: AM_CONDITIONAL
configure.ac:302: error: possibly undefined macro: AC_MSG_WARN
configure.ac:334: error: possibly undefined macro: AC_CHECK_ICU
configure.ac:352: error: possibly undefined macro: AC_CHECK_CURL
Re: cors branch testing
Posted by "john.tiger" <jo...@gmail.com>.
@ randall, oh, good catch - there is a system installed package - will
stop it - in fact, will delete it (this is a test machine and only want
to run couch with cors on it). onward and upward.
On 11/04/2012 01:57 PM, Jan Lehnardt wrote:
> On 04.11.2012, at 21:41, Randall Leeds <ra...@gmail.com> wrote:
>
>> I believe the default configuration of "make install" will install in
>> /usr/local. If you have files in /etc (instead of /usr/local/etc), then It
>> sounds like there is a system-installed couchdb package.
>>
>> One way to test is to run "make dev" and then you can launch CouchDB from
>> the source tree without installing by running "./utils/run". Make sure any
>> system-wide couchdb is stopped. The configuration files will be in
>> "etc/couchdb" in the source tree after building.
> Note that when running make dev, which is definitely recommended, that the respective .ini files are etc/couchdb/default_dev.ini & local_dev.ini
>
> Cheers
> Jan
> --
>
>
>
>>
>> On Sun, Nov 4, 2012 at 11:09 AM, john.tiger <jo...@gmail.com>wrote:
>>
>>> On 11/04/2012 08:19 AM, Benoit Chesneau wrote:
>>>
>>>> On Sun, Nov 4, 2012 at 4:07 PM, john.tiger <jo...@gmail.com>
>>>> 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 files - meanwhile we'll just add
>>>>> and continue testing.
>>>>>
>>>>> Are you using the correct branch ? It should be there after the
>>>> bootstrap.
>>> yes, in the right branch - the branch /etc folder has default.ini with the
>>> cors_enabled line - so apparently the bootstrap is not overwriting the
>>> system /etc/couchdb/default.ini file or this happened in make install -
>>> not sure - ran both with sudo so should not be a permission thing
>>>
>>>
>>>
>>>
>>>
>>>> - benoīt
Re: cors branch testing
Posted by Jan Lehnardt <ja...@php.net>.
On 04.11.2012, at 21:41, Randall Leeds <ra...@gmail.com> wrote:
> I believe the default configuration of "make install" will install in
> /usr/local. If you have files in /etc (instead of /usr/local/etc), then It
> sounds like there is a system-installed couchdb package.
>
> One way to test is to run "make dev" and then you can launch CouchDB from
> the source tree without installing by running "./utils/run". Make sure any
> system-wide couchdb is stopped. The configuration files will be in
> "etc/couchdb" in the source tree after building.
Note that when running make dev, which is definitely recommended, that the respective .ini files are etc/couchdb/default_dev.ini & local_dev.ini
Cheers
Jan
--
>
>
> On Sun, Nov 4, 2012 at 11:09 AM, john.tiger <jo...@gmail.com>wrote:
>
>> On 11/04/2012 08:19 AM, Benoit Chesneau wrote:
>>
>>> On Sun, Nov 4, 2012 at 4:07 PM, john.tiger <jo...@gmail.com>
>>> 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 files - meanwhile we'll just add
>>>> and continue testing.
>>>>
>>>> Are you using the correct branch ? It should be there after the
>>> bootstrap.
>>
>> yes, in the right branch - the branch /etc folder has default.ini with the
>> cors_enabled line - so apparently the bootstrap is not overwriting the
>> system /etc/couchdb/default.ini file or this happened in make install -
>> not sure - ran both with sudo so should not be a permission thing
>>
>>
>>
>>
>>
>>> - benoīt
>>
Re: cors branch testing
Posted by Randall Leeds <ra...@gmail.com>.
I believe the default configuration of "make install" will install in
/usr/local. If you have files in /etc (instead of /usr/local/etc), then It
sounds like there is a system-installed couchdb package.
One way to test is to run "make dev" and then you can launch CouchDB from
the source tree without installing by running "./utils/run". Make sure any
system-wide couchdb is stopped. The configuration files will be in
"etc/couchdb" in the source tree after building.
On Sun, Nov 4, 2012 at 11:09 AM, john.tiger <jo...@gmail.com>wrote:
> On 11/04/2012 08:19 AM, Benoit Chesneau wrote:
>
>> On Sun, Nov 4, 2012 at 4:07 PM, john.tiger <jo...@gmail.com>
>> 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 files - meanwhile we'll just add
>>> and continue testing.
>>>
>>> Are you using the correct branch ? It should be there after the
>> bootstrap.
>>
>
> yes, in the right branch - the branch /etc folder has default.ini with the
> cors_enabled line - so apparently the bootstrap is not overwriting the
> system /etc/couchdb/default.ini file or this happened in make install -
> not sure - ran both with sudo so should not be a permission thing
>
>
>
>
>
>> - benoīt
>>
>>
>
Re: cors branch testing
Posted by "john.tiger" <jo...@gmail.com>.
On 11/04/2012 08:19 AM, Benoit Chesneau wrote:
> On Sun, Nov 4, 2012 at 4:07 PM, john.tiger <jo...@gmail.com> 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 files - meanwhile we'll just add
>> and continue testing.
>>
> Are you using the correct branch ? It should be there after the bootstrap.
yes, in the right branch - the branch /etc folder has default.ini with
the cors_enabled line - so apparently the bootstrap is not overwriting
the system /etc/couchdb/default.ini file or this happened in make
install - not sure - ran both with sudo so should not be a permission thing
>
> - benoît
>
Re: cors branch testing
Posted by Benoit Chesneau <bc...@gmail.com>.
On Sun, Nov 4, 2012 at 4:07 PM, john.tiger <jo...@gmail.com> 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 files - meanwhile we'll just add
> and continue testing.
>
Are you using the correct branch ? It should be there after the bootstrap.
- benoît
Re: cors branch testing
Posted by "john.tiger" <jo...@gmail.com>.
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 <jo...@gmail.com> wrote:
>> 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 undefined macro: AM_CONFIG_HEADER
>> If this token and others are legitimate, please use m4_pattern_allow.
>> See the Autoconf documentation.
>> configure.ac:25: error: possibly undefined macro: AM_INIT_AUTOMAKE
>> configure.ac:28: error: possibly undefined macro: AC_ENABLE_SHARED
>> configure.ac:29: error: possibly undefined macro: AC_DISABLE_STATIC
>> configure.ac:33: error: possibly undefined macro: AC_PROG_LIBTOOL
>> configure.ac:61: error: possibly undefined macro: AC_DEFINE
>> configure.ac:207: error: possibly undefined macro: AM_CONDITIONAL
>> configure.ac:302: error: possibly undefined macro: AC_MSG_WARN
>> configure.ac:334: error: possibly undefined macro: AC_CHECK_ICU
>> configure.ac:352: error: possibly undefined macro: AC_CHECK_CURL
>>
okay, from @randall, used ./bootstrap to create configure file. sudo
./configure, then sudo make and sudo make install ran okay except for:
gzip -9 < README > README.gz
fatal: ambiguous argument '6c976bd..HEAD': unknown revision or path not
in the working tree.
Use '--' to separate paths from revisions
but this might have to do with libs in this linuxmint 12.04 (ubuntu
12.04 based) - oh, how I wish i could install debian unstable on this
macbook 2.1 (:
re @dch - also in this vendor mix, the ini files are under /etc/couchdb
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 files - meanwhile we'll
just add and continue testing.
Re: cors branch testing
Posted by "john.tiger" <jo...@gmail.com>.
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 on limiting to maybe a certain domain. for
example - if we are running a html 5/jquery app on either default (no
port) or on a certain port say 8080 - and if couch is on standard 5984
should the "allowed" port be 8080 or 5984 ?
Re: cors branch testing
Posted by Benoit Chesneau <bc...@gmail.com>.
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 <jo...@gmail.com> wrote:
> 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 undefined macro: AM_CONFIG_HEADER
> If this token and others are legitimate, please use m4_pattern_allow.
> See the Autoconf documentation.
> configure.ac:25: error: possibly undefined macro: AM_INIT_AUTOMAKE
> configure.ac:28: error: possibly undefined macro: AC_ENABLE_SHARED
> configure.ac:29: error: possibly undefined macro: AC_DISABLE_STATIC
> configure.ac:33: error: possibly undefined macro: AC_PROG_LIBTOOL
> configure.ac:61: error: possibly undefined macro: AC_DEFINE
> configure.ac:207: error: possibly undefined macro: AM_CONDITIONAL
> configure.ac:302: error: possibly undefined macro: AC_MSG_WARN
> configure.ac:334: error: possibly undefined macro: AC_CHECK_ICU
> configure.ac:352: error: possibly undefined macro: AC_CHECK_CURL
>
Re: cors branch testing
Posted by Dave Cottlehuber <dc...@jsonified.com>.
On 4 November 2012 02:44, john.tiger <jo...@gmail.com> wrote:
> a few questions so far:
> 1) where does "cors_enable=true get set - tried to do sudo ./configure
> --cors_enable.... that didn't work
Thanks for giving this a whirl! I suspect you may be the first pilot
user so really appreciate all those "Y U NO WORK" questions. Keep'em
coming please!!
http://wiki.apache.org/couchdb/CORS#Enabling_CORS
Your local.ini file will be something like
/usr/local/etc/couchdb/local.ini depending on OS & how you installed
couchdb. It's the same file you'll have set bind_address = 0.0.0.0 or
similar in. Here's mine:
[httpd]
;port = 5984
;bind_address = 127.0.0.1
bind_address = 0.0.0.0
enable_cors = true
I think that's all you're going to need.
> 2) ini file ? is that a windows thing ? - also would be helpful to have an
> example of that
See wiki url above, let me know if that's sufficient.
> 3) using autoconf gave the following:
Aargh. Yuck. autoconf fun.
I'm guessing you need a new auto* version. Not sure how you'd need to
upgrade, reply back with your OS/platform and hopefully somebody can
help you from here.
> configure.ac:22: error: possibly undefined macro: AM_CONFIG_HEADER
A+
Dave