[GitHub] LastStarDust commented on issue #1378: Purge throws "this feature is not yet implemented"
LastStarDust commented on issue #1378: Purge throws "this feature is not yet implemented" URL: https://github.com/apache/couchdb/issues/1378#issuecomment-422194411 Ok clear! I will downgrade to 1.x for the time being. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali commented on issue #1604: couchup does not copy database permissions
wohali commented on issue #1604: couchup does not copy database permissions URL: https://github.com/apache/couchdb/issues/1604#issuecomment-422193330 Confirmed, this is a concern. We need to manually grab the _security object and replicate it over. The problem is that if your _users database doesn't have the same content, the security settings may prevent appropriate access to the database for non-server-admins. Would you be OK if this was optional functionality enabled with a command line flag? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali commented on issue #1602: Remove runtime configurability of core system components
wohali commented on issue #1602: Remove runtime configurability of core system components URL: https://github.com/apache/couchdb/pull/1602#issuecomment-422188351 +1 on the env var approach vs. app files - this makes modification in e.g. Docker containers very straightforward, as well as systemd unit files / init files. "Why not both" is totally fine for me :) This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] janl commented on a change in pull request #1602: Remove runtime configurability of core system components
janl commented on a change in pull request #1602: Remove runtime
configurability of core system components
URL: https://github.com/apache/couchdb/pull/1602#discussion_r218150964
##
File path: src/couch/src/couch_httpd_vhost.erl
##
@@ -394,25 +390,23 @@ handle_config_terminate(_Server, _Reason, _State) ->
load_conf() ->
%% get vhost globals
-VHostGlobals = re:split(config:get("httpd",
-"vhost_global_handlers",""), "\\s*,\\s*",[{return, list}]),
+VHostGlobals = re:split("_utils, _uuids, _session, _users", "\\s*,\\s*",
Review comment:
good call, might have to keep it dynamic to allow `couch.app`
configurability as per
https://github.com/apache/couchdb/pull/1602#issuecomment-42200131 but good
call2
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] janl commented on a change in pull request #1602: Remove runtime configurability of core system components
janl commented on a change in pull request #1602: Remove runtime
configurability of core system components
URL: https://github.com/apache/couchdb/pull/1602#discussion_r218150964
##
File path: src/couch/src/couch_httpd_vhost.erl
##
@@ -394,25 +390,23 @@ handle_config_terminate(_Server, _Reason, _State) ->
load_conf() ->
%% get vhost globals
-VHostGlobals = re:split(config:get("httpd",
-"vhost_global_handlers",""), "\\s*,\\s*",[{return, list}]),
+VHostGlobals = re:split("_utils, _uuids, _session, _users", "\\s*,\\s*",
Review comment:
good call, might have to keep it dynamic to allow `couch.app`
configurability as per
https://github.com/apache/couchdb/pull/1602#issuecomment-42200131 but good
call
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] peterkga opened a new issue #1604: couchup does not copy database permissions
peterkga opened a new issue #1604: couchup does not copy database permissions URL: https://github.com/apache/couchdb/issues/1604 couchup does not seem to copy database permissions from 1.6.1 to 2.2.0 ## Expected Behavior I would expect the system to copy not only the data but also any permissions assigned to the database. ## Current Behavior ## Possible Solution ## Steps to Reproduce (for bugs) 1. upgrade couchdb from 1.6.1 to 2.2.0 2. startup couchdb 3. run coucup replicate -a 4.when viewing the couchdb instance on a web browser no permissions as replicated ## Context ## Your Environment * Version used: 2.2.0 * Browser Name and version: google chrome * Operating System and version (desktop or mobile): RHEL7.4 * Link to your project: n/a This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] iilyak commented on a change in pull request #1602: Remove runtime configurability of core system components
iilyak commented on a change in pull request #1602: Remove runtime
configurability of core system components
URL: https://github.com/apache/couchdb/pull/1602#discussion_r218140330
##
File path: src/couch/src/couch_httpd_vhost.erl
##
@@ -394,25 +390,23 @@ handle_config_terminate(_Server, _Reason, _State) ->
load_conf() ->
%% get vhost globals
-VHostGlobals = re:split(config:get("httpd",
-"vhost_global_handlers",""), "\\s*,\\s*",[{return, list}]),
+VHostGlobals = re:split("_utils, _uuids, _session, _users", "\\s*,\\s*",
Review comment:
Did you consider hardcoding it?:
```
VHostGlobals = ["_utils","_uuids","_session","_users"]
```
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] janl commented on a change in pull request #1602: Remove runtime configurability of core system components
janl commented on a change in pull request #1602: Remove runtime
configurability of core system components
URL: https://github.com/apache/couchdb/pull/1602#discussion_r218133665
##
File path: src/couch/src/couch_proc_manager.erl
##
@@ -372,12 +372,59 @@ new_proc(Client) ->
end,
exit(Resp).
+get_env_for_spec(Spec, Target) ->
+% loop over os:getenv(), match SPEC_TARGET
+lists:filtermap(fun(VarName) ->
+SpecStr = Spec ++ Target,
+case string:tokens(VarName, "=") of
+[SpecStr, Cmd] -> {true, Cmd};
+_Else -> false
+end
+end, os:getenv()).
+
+get_query_server(LangStr) ->
+% look for COUCH_QUERY_SERVER_LANGSTR in env
+% if exists, return value, else undefined
+UpperLangString = string:to_upper(LangStr),
+case get_env_for_spec("COUCHDB_QUERY_SERVER_", UpperLangString) of
+[] -> undefined;
+[Command] -> Command
+end.
+
+native_query_server_enabled() ->
+% 1. [native_query_server] enable_erlang_query_server = true | false
+% 2. if [native_query_server] erlang == {couch_native_process, start_link,
[]} -> pretend true as well
+NativeEnabled = config:get_boolean("native_query_servers",
"enable_erlang_query_server", false),
+NativeLegacyConfig = config:get("native_query_servers", "erlang", ""),
+NativeLegacyEnabled = NativeLegacyConfig =:= "{couch_native_process,
start_link, []}",
+
+% there surely is a more elegant way to do this that eludes me at present
+case {NativeEnabled, NativeLegacyEnabled} of
Review comment:
omg thanks :D
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] wohali commented on issue #107: Can't use with jrcs/letsencrypt-nginx-proxy-companion
wohali commented on issue #107: Can't use with jrcs/letsencrypt-nginx-proxy-companion URL: https://github.com/apache/couchdb-docker/issues/107#issuecomment-422077551 should be fine once you set up users in the _users database or the ini file for admins for access. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] DREZZ3R commented on issue #107: Can't use with jrcs/letsencrypt-nginx-proxy-companion
DREZZ3R commented on issue #107: Can't use with jrcs/letsencrypt-nginx-proxy-companion URL: https://github.com/apache/couchdb-docker/issues/107#issuecomment-422076122 BTW, can you help me enabling authenthication via couchdb via URL. Doing username:passw...@app.domain.com does not work This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] janl commented on issue #1602: Remove runtime configurability of core system components
janl commented on issue #1602: Remove runtime configurability of core system components URL: https://github.com/apache/couchdb/pull/1602#issuecomment-422075745 > also noting that changing couchjs stack size is an important ability. def agree! we could introduce `[query_server_config] js_stack_size` (and other options) param, and have it apply to new instances spawned after a config change. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] rnewson commented on issue #1602: Remove runtime configurability of core system components
rnewson commented on issue #1602: Remove runtime configurability of core system components URL: https://github.com/apache/couchdb/pull/1602#issuecomment-422075300 also noting that changing couchjs stack size is an important ability. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali commented on issue #107: Can't use with jrcs/letsencrypt-nginx-proxy-companion
wohali commented on issue #107: Can't use with jrcs/letsencrypt-nginx-proxy-companion URL: https://github.com/apache/couchdb-docker/issues/107#issuecomment-422066831 You may also want to use the official nginx configuration file to ensure replication etc. work: http://docs.couchdb.org/en/stable/best-practices/nginx.html?highlight=nginx This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali edited a comment on issue #1378: Purge throws "this feature is not yet implemented"
wohali edited a comment on issue #1378: Purge throws "this feature is not yet implemented" URL: https://github.com/apache/couchdb/issues/1378#issuecomment-422066423 @LastStarDust The next released version of CouchDB will include purge functionality. Or, you can go back to CouchDB 1.x. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali commented on issue #1378: Purge throws "this feature is not yet implemented"
wohali commented on issue #1378: Purge throws "this feature is not yet implemented" URL: https://github.com/apache/couchdb/issues/1378#issuecomment-422066423 @LastStarDust The next released version of CouchDB will include purge functionality. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] nickva commented on a change in pull request #1602: Remove runtime configurability of core system components
nickva commented on a change in pull request #1602: Remove runtime
configurability of core system components
URL: https://github.com/apache/couchdb/pull/1602#discussion_r218108062
##
File path: src/couch/src/couch_proc_manager.erl
##
@@ -372,12 +372,59 @@ new_proc(Client) ->
end,
exit(Resp).
+get_env_for_spec(Spec, Target) ->
+% loop over os:getenv(), match SPEC_TARGET
+lists:filtermap(fun(VarName) ->
+SpecStr = Spec ++ Target,
+case string:tokens(VarName, "=") of
+[SpecStr, Cmd] -> {true, Cmd};
+_Else -> false
+end
+end, os:getenv()).
+
+get_query_server(LangStr) ->
+% look for COUCH_QUERY_SERVER_LANGSTR in env
+% if exists, return value, else undefined
+UpperLangString = string:to_upper(LangStr),
+case get_env_for_spec("COUCHDB_QUERY_SERVER_", UpperLangString) of
+[] -> undefined;
+[Command] -> Command
+end.
+
+native_query_server_enabled() ->
+% 1. [native_query_server] enable_erlang_query_server = true | false
+% 2. if [native_query_server] erlang == {couch_native_process, start_link,
[]} -> pretend true as well
+NativeEnabled = config:get_boolean("native_query_servers",
"enable_erlang_query_server", false),
+NativeLegacyConfig = config:get("native_query_servers", "erlang", ""),
+NativeLegacyEnabled = NativeLegacyConfig =:= "{couch_native_process,
start_link, []}",
+
+% there surely is a more elegant way to do this that eludes me at present
+case {NativeEnabled, NativeLegacyEnabled} of
Review comment:
`NativeEnabled orelse NativeLegacyEnabled` ?
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] LastStarDust commented on issue #1378: Purge throws "this feature is not yet implemented"
LastStarDust commented on issue #1378: Purge throws "this feature is not yet implemented" URL: https://github.com/apache/couchdb/issues/1378#issuecomment-422050434 @jiangphcn Thank you for the hint. Anyway I am using a single-node configuration and I am getting the same error. I tried to compile from source the master branch but I got stuck because of other errors. If possible I would like to stick using the repository version of couchdb. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] DREZZ3R edited a comment on issue #107: Can't use with jrcs/letsencrypt-nginx-proxy-companion
DREZZ3R edited a comment on issue #107: Can't use with jrcs/letsencrypt-nginx-proxy-companion URL: https://github.com/apache/couchdb-docker/issues/107#issuecomment-422040893 Ok I've got with a solution. When initializing couch, we need to specify the `VIRTUAL_PORT`. ``` docker run -e COUCHDB_USER=user \ -e COUCHDB_PASSWORD=password \ -e "VIRTUAL_HOST=app.domain.com" \ -e VIRTUAL_PORT=5984 \ -e "LETSENCRYPT_HOST=app.domain.com" \ -e "LETSENCRYPT_EMAIL=exam...@domain.com" \ --volume ~/data:/opt/couchdb/data --volume ~/etc/local.d:/opt/couchdb/etc/local.d \ --name api-couchdb --restart always -d couchdb ``` This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] DREZZ3R closed issue #107: Can't use with jrcs/letsencrypt-nginx-proxy-companion
DREZZ3R closed issue #107: Can't use with jrcs/letsencrypt-nginx-proxy-companion URL: https://github.com/apache/couchdb-docker/issues/107 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] DREZZ3R commented on issue #107: Can't use with jrcs/letsencrypt-nginx-proxy-companion
DREZZ3R commented on issue #107: Can't use with jrcs/letsencrypt-nginx-proxy-companion URL: https://github.com/apache/couchdb-docker/issues/107#issuecomment-422040893 Ok I've got with a solution. When initializing couch, we need to specify the `VIRTUAL_PORT`. ``` docker run -e COUCHDB_USER=truenet_couch \ -e COUCHDB_PASSWORD=QBm0WZ5iwr5NwmVStmIqMIcMrDXdfY33nlWAiNbgNyj871zYkDTZIQOcuMYXldhOV2Am6hSLD359xjTsLjClTkkwFwNObw7vNkAY \ -e "VIRTUAL_HOST=app.truenet.pt" \ -e VIRTUAL_PORT=5984 \ -e "LETSENCRYPT_HOST=app.truenet.pt" \ -e "LETSENCRYPT_EMAIL=jorge.c...@truenet.pt" \ --volume ~/data:/opt/couchdb/data --volume ~/etc/local.d:/opt/couchdb/etc/local.d \ --name api-couchdb --restart always -d couchdb ``` This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] DREZZ3R opened a new issue #107: Can't use with jrcs/letsencrypt-nginx-proxy-companion
DREZZ3R opened a new issue #107: Can't use with
jrcs/letsencrypt-nginx-proxy-companion
URL: https://github.com/apache/couchdb-docker/issues/107
I've been trying to use couchdb and nginx-letsencrypt. It works with my node
js server, but it won't work with couchdb. It always give 502 bad gateway. The
node.js server is in a different sub-domain.
### To start _nginx_ I use this:
```
docker run -d -p 80:80 -p 443:443 \
--name nginx-proxy \
-v /path/to/certs:/etc/nginx/certs:ro \
-v /etc/nginx/vhost.d \
-v /usr/share/nginx/html \
-v /var/run/docker.sock:/tmp/docker.sock:ro \
--label com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy \
jwilder/nginx-proxy
```
### To start _letsencrypt-nginx-proxy-companion_ I use:
```
docker run -d \
--name nginx-proxy-letsencrypt \
-v /path/to/certs:/etc/nginx/certs:rw \
-v /var/run/docker.sock:/var/run/docker.sock:ro \
--volumes-from nginx-proxy \
jrcs/letsencrypt-nginx-proxy-companion
```
### To start couchdb I use:
```
docker run -e COUCHDB_USER=user\
-e COUCHDB_PASSWORD=password \
-e "VIRTUAL_HOST=app.domain.com" \
-e "LETSENCRYPT_HOST=app.domain.com" \
-e "LETSENCRYPT_EMAIL=exam...@domain.com" \
--volume ~/data:/opt/couchdb/data --volume
~/etc/local.d:/opt/couchdb/etc/local.d \
--name api-couchdb --restart always -d couchdb
```
The generated config file inside **nginx-proxy** container
`/etc/nginx/conf.d/default` has this:
NOTE: I tried to remove the "down" in the upstream section but didn't work.
Also tried to remove http2 but didn't work.
```
# app.domain.com
upstream app.domain.com {
## Can be connected with "bridge" network
# api-couchdb
server 172.17.0.2 down;
}
server {
server_name app.domain.com;
listen 80 ;
access_log /var/log/nginx/access.log vhost;
return 301 https://$host$request_uri;
}
server {
server_name app.domain.com;
listen 443 ssl http2 ;
access_log /var/log/nginx/access.log vhost;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers
'ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:!DSS';
ssl_prefer_server_ciphers on;
ssl_session_timeout 5m;
ssl_session_cache shared:SSL:50m;
ssl_session_tickets off;
ssl_certificate /etc/nginx/certs/app.domain.com.crt;
ssl_certificate_key /etc/nginx/certs/app.domain.com.key;
ssl_dhparam /etc/nginx/certs/app.domain.com.dhparam.pem;
ssl_stapling on;
ssl_stapling_verify on;
ssl_trusted_certificate /etc/nginx/certs/app.domain.com.chain.pem;
add_header Strict-Transport-Security "max-age=31536000" always;
include /etc/nginx/vhost.d/default;
location / {
proxy_pass http://app.domain.com;
}
}
```
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] jiangphcn commented on issue #1378: Purge throws "this feature is not yet implemented"
jiangphcn commented on issue #1378: Purge throws "this feature is not yet implemented" URL: https://github.com/apache/couchdb/issues/1378#issuecomment-422020455 @LastStarDust Clustered purge is not in CouchDB 2.2, but was just merged to CouchDB master branch. You can see more information about this new feature from https://github.com/apache/couchdb-documentation/pull/285/files. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] LastStarDust edited a comment on issue #1378: Purge throws "this feature is not yet implemented"
LastStarDust edited a comment on issue #1378: Purge throws "this feature is not yet implemented" URL: https://github.com/apache/couchdb/issues/1378#issuecomment-422013135 Hello! I am experiencing the same problem on a single-node configuration of CouchDB (not clustered). I am not using CouchDB directly but only through another application called [Pyrame](http://llr.in2p3.fr/sites/pyrame/documentation/_modules/cmd_rundb.html#del_acq_rundb). In the link, you can look at the portion of code that throws the error. In turn, this application makes use of the `purge` function offered by the [couchdb-python](https://github.com/djc/couchdb-python) package. I am a physicists and not a server administrator so my knowledge of the inner working of CouchDB is very limited. I read from above that there is a workaround but I cannot understand how to use it. Could you please explain to me how to modify the Pyrame or couchdb-python code to make use of the workaround? I know that it is not strictly "your job" to do so and apologize for the strange request. I am using CouchDB 2.2.0~bionic and Ubuntu 18.04. CouchDB was installed from the repositories. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] LastStarDust edited a comment on issue #1378: Purge throws "this feature is not yet implemented"
LastStarDust edited a comment on issue #1378: Purge throws "this feature is not yet implemented" URL: https://github.com/apache/couchdb/issues/1378#issuecomment-422013135 Hello! I am experiencing the same problem on a single-node configuration of CouchDB (not clustered). I am not using CouchDB directly but only through another application called [Pyrame](http://llr.in2p3.fr/sites/pyrame/documentation/_modules/cmd_rundb.html#del_acq_rundb). In the link, you can look at the portion of code that throws the error. In turn, this application makes use of the `purge` function offered by the [couchdb-python](https://github.com/djc/couchdb-python) package. I am a Physicists and not a server administrator so my knowledge of the inner working of CouchDB is very limited. I read from above that there is a workaround but I cannot understand how to use it. Could you please explain to me how to modify the Pyrame or couchdb-python code to make use of the workaround? I know that it is not strictly "your job" to do so and apologize for the strange request. I am using CouchDB 2.2.0~bionic and Ubuntu 18.04. CouchDB was installed from the repositories. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] LastStarDust edited a comment on issue #1378: Purge throws "this feature is not yet implemented"
LastStarDust edited a comment on issue #1378: Purge throws "this feature is not yet implemented" URL: https://github.com/apache/couchdb/issues/1378#issuecomment-422013135 Hello! I am experiencing the same problem on a single-node configuration of CouchDB (not clustered). I am not using CouchDB directly but only through another application called [Pyrame](http://llr.in2p3.fr/sites/pyrame/documentation/_modules/cmd_rundb.html#del_acq_rundb). In the link, you can look at the portion of code that throws the error. In turn, this application makes use of the `purge` function offered by the [couchdb-python](https://github.com/djc/couchdb-python) package. I am a Physicists and not a server administrator so my knowledge of the inner working of CouchDB is very limited. I read from above that there is a workaround but I cannot understand how to use it. Could you please explain to me how to modify the Pyrame or couchdb-python code to make use of the workaround? I know that it is not strictly "your job" to do so and apologize for the strange request. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] LastStarDust commented on issue #1378: Purge throws "this feature is not yet implemented"
LastStarDust commented on issue #1378: Purge throws "this feature is not yet implemented" URL: https://github.com/apache/couchdb/issues/1378#issuecomment-422013135 Hello! I am experiencing the same problem on a single-node configuration of CouchDB (not clustered). I am not using CouchDB directly but only through another application called [Pyrame](http://llr.in2p3.fr/sites/pyrame/documentation/_modules/cmd_rundb.html#del_acq_rundb). In the link, you can look at the portion of code that throws the error. In turn this application makes use of the purge function offered by the [couchdb-python](https://github.com/djc/couchdb-python) package. I am a Physicists and not a server administrator so my knowledge of the inner working of CouchDB is very limited. I read from above that there is a workaround but I cannot understand how to use it. Could you please explain to me how to modify the Pyrame or couch-python code to make use of the workaround? I know that it is not strictly "your job" to do so and apologize for the strange request. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] rnewson edited a comment on issue #1602: Remove runtime configurability of core system components
rnewson edited a comment on issue #1602: Remove runtime configurability of core
system components
URL: https://github.com/apache/couchdb/pull/1602#issuecomment-422001312
{application,appname, [
{description, "blah"},
{vsn, git},
{registered,[]},
{applications,[kernel,stdlib,config,couch_stats]},
{mod,{appname_app,[]}},
{env, [
{httpd_global_handlers, [
{_all_dbs, couch_httpd_misc_handlers, handle_all_dbs_req},
...},
...
]}
]}.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] rnewson edited a comment on issue #1602: Remove runtime configurability of core system components
rnewson edited a comment on issue #1602: Remove runtime configurability of core
system components
URL: https://github.com/apache/couchdb/pull/1602#issuecomment-422001312
> {application,appname, [
> {description, "blah"},
> {vsn, git},
> {registered,[]},
> {applications,[kernel,stdlib,config,couch_stats]},
> {mod,{appname_app,[]}},
> {env, [
> {httpd_global_handlers, [
> {_all_dbs, couch_httpd_misc_handlers, handle_all_dbs_req},
> ...},
> ...
> ]}
> ]}.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] rnewson edited a comment on issue #1602: Remove runtime configurability of core system components
rnewson edited a comment on issue #1602: Remove runtime configurability of core
system components
URL: https://github.com/apache/couchdb/pull/1602#issuecomment-422001312
{application,appname, [
{description, "blah"},
{vsn, git},
{registered,[]},
{applications,[kernel,stdlib,config,couch_stats]},
{mod,{appname_app,[]}},
{env, [
{httpd_global_handlers, [
{_all_dbs, couch_httpd_misc_handlers, handle_all_dbs_req},
...},
...
]}
]}.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] rnewson commented on issue #1602: Remove runtime configurability of core system components
rnewson commented on issue #1602: Remove runtime configurability of core system
components
URL: https://github.com/apache/couchdb/pull/1602#issuecomment-422001312
`{application,appname, [
{description, "blah"},
{vsn, git},
{registered,[]},
{applications,[kernel,stdlib,config,couch_stats]},
{mod,{appname_app,[]}},
{env, [
{httpd_global_handlers, [
{_all_dbs, couch_httpd_misc_handlers, handle_all_dbs_req},
...},
...
]}
]}.`
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] janl commented on issue #1602: Remove runtime configurability of core system components
janl commented on issue #1602: Remove runtime configurability of core system components URL: https://github.com/apache/couchdb/pull/1602#issuecomment-421993464 @rnewson I’m happy to add query server defaults to the .app file for your use-case. I *also* want to retain the possibility for folks who run binary builds to add their third party query servers via env vars. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] rnewson commented on issue #1602: Remove runtime configurability of core system components
rnewson commented on issue #1602: Remove runtime configurability of core system components URL: https://github.com/apache/couchdb/pull/1602#issuecomment-421988917 I'm +1 on removing runtime configurability but would prefer that the configuration is expressed in the .app files of the respective erlang applications. This will allow package maintainers (etc) to more easily tweak at build time if necessary without introducing the runtime malleability that concerns us. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
