kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/databases/couchdb/PLIST

362 lines
18 KiB
Text
Raw Normal View History

couchdb: Upgrade to 2.3.1. Now works with current Erlang. Summary of changes between 2.1.x and 2.3.x are listed below. For a more readable version please see the following URLs: http://docs.couchdb.org/en/latest/whatsnew/2.3.html http://docs.couchdb.org/en/latest/whatsnew/2.2.html http://docs.couchdb.org/en/latest/whatsnew/2.1.html 2.3.x Branch Upgrade Notes #1602: To improve security, there have been major changes in the configuration of query servers, SSL support, and HTTP global handlers: Query servers are NO LONGER DEFINED in the .ini files, and can no longer be altered at run-time. The JavaScript and CoffeeScript query servers continue to be enabled by default. Setup differences have been moved from default.ini to the couchdb and couchdb.cmd start scripts respectively. Additional query servers can now be configured using environment variables: export COUCHDB_QUERY_SERVER_PYTHON="/path/to/python/query/server.py with args" couchdb where the last segment in the environment variable (_PYTHON) matches the usual lowercase(!) query language in the design doc language field (here, python.) Multiple query servers can be configured by using more environment variables. You can also override the default servers if you need to set command- line options (such as couchjs stack size): export COUCHDB_QUERY_SERVER_JAVASCRIPT="/path/to/couchjs /path/to/main.js -S <STACKSIZE>" couchdb The mango query server continues to be enabled by default. The Erlang query server continues to be disabled by default. This change adds a [native_query_servers] enable_erlang_query_server = BOOL setting (defaults to false) to enable the Erlang query server. If the legacy configuration for enabling the query server is detected, that is counted as a true setting as well, so existing configurations continue to work just fine. SSL Support Enabling SSL support in the ini file is now easier: [ssl] enable = true If the legacy httpsd configuration is found in your ini file, this will still enable SSL support, so existing configurations do not need to be changed. HTTP global handlers These are no longer defined in the default.ini file, but have been moved to the couch.app context. If you need to customize your handlers, you can modify the app context using a couchdb.config file as usual. #1602: Also to improve security, the deprecated os_daemons and couch_httpd_proxy functionality has been completely removed ahead of the planned CouchDB 3.0 release. We recommend the use of OS-level daemons such as runit, sysvinit, systemd, upstart, etc. to launch and maintain OS daemons instead, and the use of a reverse proxy server in front of CouchDB (such as haproxy) to proxy access to other services or domains alongside CouchDB. #1543: The node-local (default port 5986) /_restart endpoint has been replaced by the clustered (default port 5984) endpoint /_node/$node/_restart and /_node/_local/_restart endpoints. The node-local endpoint has been removed. #1764: All python scripts shipped with CouchDB, including couchup and the dev/run development cluster script, now specify and require Python 3.x. #1396: CouchDB is now compatible with Erlang 21.x. #1680: The embedded version of rebar used to build CouchDB has been updated to the last version of rebar2 available. This assists in building on non-x86 platforms. #1857: Refuse building with known bad versions of Erlang. 2.2.x Branch Upgrade Notes The minimum supported version of Erlang is now 17, not R16B03. Support for Erlang 21 is still ongoing and will be provided in a future release. The CouchDB replication client can now use the /_session endpoint when authenticating against remote CouchDB instances, improving performance since re-authorization does not have to be performed with every request. Because of this performance improvement, it is recommended to increase the PBKDF2 work factor beyond the default 10 to a modern default such as 10000. This is done via the local ini file setting [couch_httpd_auth] iterations = 10000. Do not do this if an older version of CouchDB is replicating TO this instance or cluster regularly, since CouchDB < 2.2.0 must perform authentication on every request and replication performance will suffer. A future version will make this increased number of iterations a default. #820, #1032: Multiple queries can now be made at the POST /{db}/_all_docs/queries, POST /{db}/_design_docs/queries and POST /{db}/_local_docs/queries endpoints. Also, a new endpoint POST /{db}/_design/{ddoc}/_view/{view}/queries has been introduced to replace the ?queries parameter formerly provided for making multiple queries to a view. The old ?queries parameter is now deprecated and will be removed in a future release of CouchDB. The maximum http request limit, which had been lowered in 2.1.0, has been re-raised to a 4GB limit for now. (#1446). Ongoing discussion about the path forward for future releases is available in #1200 and #1253. #1118: The least recently used (LRU) cache of databases is now only updated on database write, not read. This has lead to significant performance enhancements on very busy clusters. To restore the previous behaviour, your local ini file can contain the block [couchdb] update_lru_on_read = true. #1153: The CouchDB replicator can now make use of the /_session endpoint rather than relying entirely on HTTP basic authentication headers. This can greatly improve replication performance. We encourage you to upgrade any nodes or clusters that regularly act as replication clients to use this new feature, which is enabled by default (#1462). #1283: The [couchdb] enable_database_recovery feature, which only soft-deletes databases in response to a DELETE /{db} call, is now documented in default.ini. #1330: CouchDB externals and OS daemons are now officially deprecated and no longer documented. Support for these features will be completely removed in a future release of CouchDB (probably 3.0.0). #1436: CouchDB proxy authentication now uses a proper chttpd_auth module, simplifying configuration in local ini files. While this is not a backward- compatible breaking change, it is best to update your local ini files to reference the new {chttpd_auth, proxy_authentication_handler} handler rather than the couch_httpd_auth version, as couch_httpd is in the process of being deprecated completely. #1476, #1477: The obsolete update_notification feature, which was replaced by /{db}/_changes feeds c. CouchDB 1.2, has been completely removed. This feature never worked in 2.0 for databases, only for shards, making it effectively useless.
2019-09-06 11:10:47 +02:00
@comment $NetBSD: PLIST,v 1.10 2019/09/06 09:10:47 jperkin Exp $
Import couchdb-1.0.1 as databases/couchdb. Apache CouchDB is a distributed, fault-tolerant and schema-free document- oriented database accessible via a RESTful HTTP/JSON API. Among other features, it provides robust, incremental replication with bi-directional conflict detection and resolution, and is queryable and indexable using a table-oriented view engine with JavaScript acting as the default view definition language. CouchDB is written in Erlang, but can be easily accessed from any environment that provides means to make HTTP requests. There are a multitude of third-party client libraries that make this even easier for a variety of programming languages and environments. (Based on wip/couchdb.)
2010-09-21 14:11:39 +02:00
bin/couchdb
bin/couchjs
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/releases/${PKGVERSION}/couchdb.boot
couchdb/releases/${PKGVERSION}/couchdb.rel
couchdb/releases/${PKGVERSION}/couchdb.script
couchdb/releases/${PKGVERSION}/start_clean.boot
couchdb/releases/${PKGVERSION}/start_clean.rel
couchdb/releases/${PKGVERSION}/start_clean.script
couchdb/releases/${PKGVERSION}/sys.config
couchdb/releases/${PKGVERSION}/vm.args
couchdb/releases/RELEASES
couchdb/releases/start_erl.data
Update databases/couchdb to 2.1.1. couchdb 2.1.1 - CouchDB now supports compilation and running under Erlang/OTP 20.x - The couch_peruser functionality is now really fixed - The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customized via the ini file - It is now possible to modify shard maps for system databases - Due to an Erlang bug (ERL-343), invalid paths can be returned if volumes are mounted containing whitespace in their name (fixed) - The current node's local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.- The Dockerfile in the source repository has been retired - Fauxton now uses a version of React with a BSD license. - CouchDB now no longer decompresses documents just to determine their uncompressed size - The design document cache (ddoc_cache) has been rewritten to improve performance - Mango now supports partial indexes - Mango queries can now be paginated - Mango _find accepts an execution_stats parameter - Mango now requires that all of the fields in a candidate index must exist in a query's selector - Other minor improvements. couchdb 2.1.0 - The Mango _find endpoint supports a new combination operator, $allMatch. - New scheduling replicator. - Other minor improvements. See changelog for the 2.1.x branch for more: http://docs.couchdb.org/en/latest/whatsnew/2.1.html
2017-11-07 16:33:27 +01:00
couchdb/share/server/main-coffee.js
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/share/server/main.js
couchdb: Upgrade to 2.3.1. Now works with current Erlang. Summary of changes between 2.1.x and 2.3.x are listed below. For a more readable version please see the following URLs: http://docs.couchdb.org/en/latest/whatsnew/2.3.html http://docs.couchdb.org/en/latest/whatsnew/2.2.html http://docs.couchdb.org/en/latest/whatsnew/2.1.html 2.3.x Branch Upgrade Notes #1602: To improve security, there have been major changes in the configuration of query servers, SSL support, and HTTP global handlers: Query servers are NO LONGER DEFINED in the .ini files, and can no longer be altered at run-time. The JavaScript and CoffeeScript query servers continue to be enabled by default. Setup differences have been moved from default.ini to the couchdb and couchdb.cmd start scripts respectively. Additional query servers can now be configured using environment variables: export COUCHDB_QUERY_SERVER_PYTHON="/path/to/python/query/server.py with args" couchdb where the last segment in the environment variable (_PYTHON) matches the usual lowercase(!) query language in the design doc language field (here, python.) Multiple query servers can be configured by using more environment variables. You can also override the default servers if you need to set command- line options (such as couchjs stack size): export COUCHDB_QUERY_SERVER_JAVASCRIPT="/path/to/couchjs /path/to/main.js -S <STACKSIZE>" couchdb The mango query server continues to be enabled by default. The Erlang query server continues to be disabled by default. This change adds a [native_query_servers] enable_erlang_query_server = BOOL setting (defaults to false) to enable the Erlang query server. If the legacy configuration for enabling the query server is detected, that is counted as a true setting as well, so existing configurations continue to work just fine. SSL Support Enabling SSL support in the ini file is now easier: [ssl] enable = true If the legacy httpsd configuration is found in your ini file, this will still enable SSL support, so existing configurations do not need to be changed. HTTP global handlers These are no longer defined in the default.ini file, but have been moved to the couch.app context. If you need to customize your handlers, you can modify the app context using a couchdb.config file as usual. #1602: Also to improve security, the deprecated os_daemons and couch_httpd_proxy functionality has been completely removed ahead of the planned CouchDB 3.0 release. We recommend the use of OS-level daemons such as runit, sysvinit, systemd, upstart, etc. to launch and maintain OS daemons instead, and the use of a reverse proxy server in front of CouchDB (such as haproxy) to proxy access to other services or domains alongside CouchDB. #1543: The node-local (default port 5986) /_restart endpoint has been replaced by the clustered (default port 5984) endpoint /_node/$node/_restart and /_node/_local/_restart endpoints. The node-local endpoint has been removed. #1764: All python scripts shipped with CouchDB, including couchup and the dev/run development cluster script, now specify and require Python 3.x. #1396: CouchDB is now compatible with Erlang 21.x. #1680: The embedded version of rebar used to build CouchDB has been updated to the last version of rebar2 available. This assists in building on non-x86 platforms. #1857: Refuse building with known bad versions of Erlang. 2.2.x Branch Upgrade Notes The minimum supported version of Erlang is now 17, not R16B03. Support for Erlang 21 is still ongoing and will be provided in a future release. The CouchDB replication client can now use the /_session endpoint when authenticating against remote CouchDB instances, improving performance since re-authorization does not have to be performed with every request. Because of this performance improvement, it is recommended to increase the PBKDF2 work factor beyond the default 10 to a modern default such as 10000. This is done via the local ini file setting [couch_httpd_auth] iterations = 10000. Do not do this if an older version of CouchDB is replicating TO this instance or cluster regularly, since CouchDB < 2.2.0 must perform authentication on every request and replication performance will suffer. A future version will make this increased number of iterations a default. #820, #1032: Multiple queries can now be made at the POST /{db}/_all_docs/queries, POST /{db}/_design_docs/queries and POST /{db}/_local_docs/queries endpoints. Also, a new endpoint POST /{db}/_design/{ddoc}/_view/{view}/queries has been introduced to replace the ?queries parameter formerly provided for making multiple queries to a view. The old ?queries parameter is now deprecated and will be removed in a future release of CouchDB. The maximum http request limit, which had been lowered in 2.1.0, has been re-raised to a 4GB limit for now. (#1446). Ongoing discussion about the path forward for future releases is available in #1200 and #1253. #1118: The least recently used (LRU) cache of databases is now only updated on database write, not read. This has lead to significant performance enhancements on very busy clusters. To restore the previous behaviour, your local ini file can contain the block [couchdb] update_lru_on_read = true. #1153: The CouchDB replicator can now make use of the /_session endpoint rather than relying entirely on HTTP basic authentication headers. This can greatly improve replication performance. We encourage you to upgrade any nodes or clusters that regularly act as replication clients to use this new feature, which is enabled by default (#1462). #1283: The [couchdb] enable_database_recovery feature, which only soft-deletes databases in response to a DELETE /{db} call, is now documented in default.ini. #1330: CouchDB externals and OS daemons are now officially deprecated and no longer documented. Support for these features will be completely removed in a future release of CouchDB (probably 3.0.0). #1436: CouchDB proxy authentication now uses a proper chttpd_auth module, simplifying configuration in local ini files. While this is not a backward- compatible breaking change, it is best to update your local ini files to reference the new {chttpd_auth, proxy_authentication_handler} handler rather than the couch_httpd_auth version, as couch_httpd is in the process of being deprecated completely. #1476, #1477: The obsolete update_notification feature, which was replaced by /{db}/_changes feeds c. CouchDB 1.2, has been completely removed. This feature never worked in 2.0 for databases, only for shards, making it effectively useless.
2019-09-06 11:10:47 +02:00
couchdb/share/www/dashboard.assets/css/styles.89dbadd64e69e0df7653.css
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/share/www/dashboard.assets/fonts/fauxtonicon5.eot
couchdb/share/www/dashboard.assets/fonts/fauxtonicon5.ttf
couchdb/share/www/dashboard.assets/fonts/fauxtonicon5.woff
couchdb/share/www/dashboard.assets/fonts/fontawesome-webfont.eot
couchdb/share/www/dashboard.assets/fonts/fontawesome-webfont.ttf
couchdb/share/www/dashboard.assets/fonts/fontawesome-webfont.woff
couchdb/share/www/dashboard.assets/img/CouchDB-negative-logo.png
couchdb/share/www/dashboard.assets/img/asf-feather-logo.png
couchdb/share/www/dashboard.assets/img/couch-watermark.png
couchdb/share/www/dashboard.assets/img/couchdb-logo.png
couchdb/share/www/dashboard.assets/img/fauxtonicon5.svg
couchdb/share/www/dashboard.assets/img/fontawesome-webfont.svg
couchdb/share/www/dashboard.assets/img/github.png
couchdb/share/www/dashboard.assets/img/googleplus.png
couchdb/share/www/dashboard.assets/img/linkedin.png
couchdb/share/www/dashboard.assets/img/loader.gif
couchdb/share/www/dashboard.assets/img/twitter.png
couchdb: Upgrade to 2.3.1. Now works with current Erlang. Summary of changes between 2.1.x and 2.3.x are listed below. For a more readable version please see the following URLs: http://docs.couchdb.org/en/latest/whatsnew/2.3.html http://docs.couchdb.org/en/latest/whatsnew/2.2.html http://docs.couchdb.org/en/latest/whatsnew/2.1.html 2.3.x Branch Upgrade Notes #1602: To improve security, there have been major changes in the configuration of query servers, SSL support, and HTTP global handlers: Query servers are NO LONGER DEFINED in the .ini files, and can no longer be altered at run-time. The JavaScript and CoffeeScript query servers continue to be enabled by default. Setup differences have been moved from default.ini to the couchdb and couchdb.cmd start scripts respectively. Additional query servers can now be configured using environment variables: export COUCHDB_QUERY_SERVER_PYTHON="/path/to/python/query/server.py with args" couchdb where the last segment in the environment variable (_PYTHON) matches the usual lowercase(!) query language in the design doc language field (here, python.) Multiple query servers can be configured by using more environment variables. You can also override the default servers if you need to set command- line options (such as couchjs stack size): export COUCHDB_QUERY_SERVER_JAVASCRIPT="/path/to/couchjs /path/to/main.js -S <STACKSIZE>" couchdb The mango query server continues to be enabled by default. The Erlang query server continues to be disabled by default. This change adds a [native_query_servers] enable_erlang_query_server = BOOL setting (defaults to false) to enable the Erlang query server. If the legacy configuration for enabling the query server is detected, that is counted as a true setting as well, so existing configurations continue to work just fine. SSL Support Enabling SSL support in the ini file is now easier: [ssl] enable = true If the legacy httpsd configuration is found in your ini file, this will still enable SSL support, so existing configurations do not need to be changed. HTTP global handlers These are no longer defined in the default.ini file, but have been moved to the couch.app context. If you need to customize your handlers, you can modify the app context using a couchdb.config file as usual. #1602: Also to improve security, the deprecated os_daemons and couch_httpd_proxy functionality has been completely removed ahead of the planned CouchDB 3.0 release. We recommend the use of OS-level daemons such as runit, sysvinit, systemd, upstart, etc. to launch and maintain OS daemons instead, and the use of a reverse proxy server in front of CouchDB (such as haproxy) to proxy access to other services or domains alongside CouchDB. #1543: The node-local (default port 5986) /_restart endpoint has been replaced by the clustered (default port 5984) endpoint /_node/$node/_restart and /_node/_local/_restart endpoints. The node-local endpoint has been removed. #1764: All python scripts shipped with CouchDB, including couchup and the dev/run development cluster script, now specify and require Python 3.x. #1396: CouchDB is now compatible with Erlang 21.x. #1680: The embedded version of rebar used to build CouchDB has been updated to the last version of rebar2 available. This assists in building on non-x86 platforms. #1857: Refuse building with known bad versions of Erlang. 2.2.x Branch Upgrade Notes The minimum supported version of Erlang is now 17, not R16B03. Support for Erlang 21 is still ongoing and will be provided in a future release. The CouchDB replication client can now use the /_session endpoint when authenticating against remote CouchDB instances, improving performance since re-authorization does not have to be performed with every request. Because of this performance improvement, it is recommended to increase the PBKDF2 work factor beyond the default 10 to a modern default such as 10000. This is done via the local ini file setting [couch_httpd_auth] iterations = 10000. Do not do this if an older version of CouchDB is replicating TO this instance or cluster regularly, since CouchDB < 2.2.0 must perform authentication on every request and replication performance will suffer. A future version will make this increased number of iterations a default. #820, #1032: Multiple queries can now be made at the POST /{db}/_all_docs/queries, POST /{db}/_design_docs/queries and POST /{db}/_local_docs/queries endpoints. Also, a new endpoint POST /{db}/_design/{ddoc}/_view/{view}/queries has been introduced to replace the ?queries parameter formerly provided for making multiple queries to a view. The old ?queries parameter is now deprecated and will be removed in a future release of CouchDB. The maximum http request limit, which had been lowered in 2.1.0, has been re-raised to a 4GB limit for now. (#1446). Ongoing discussion about the path forward for future releases is available in #1200 and #1253. #1118: The least recently used (LRU) cache of databases is now only updated on database write, not read. This has lead to significant performance enhancements on very busy clusters. To restore the previous behaviour, your local ini file can contain the block [couchdb] update_lru_on_read = true. #1153: The CouchDB replicator can now make use of the /_session endpoint rather than relying entirely on HTTP basic authentication headers. This can greatly improve replication performance. We encourage you to upgrade any nodes or clusters that regularly act as replication clients to use this new feature, which is enabled by default (#1462). #1283: The [couchdb] enable_database_recovery feature, which only soft-deletes databases in response to a DELETE /{db} call, is now documented in default.ini. #1330: CouchDB externals and OS daemons are now officially deprecated and no longer documented. Support for these features will be completely removed in a future release of CouchDB (probably 3.0.0). #1436: CouchDB proxy authentication now uses a proper chttpd_auth module, simplifying configuration in local ini files. While this is not a backward- compatible breaking change, it is best to update your local ini files to reference the new {chttpd_auth, proxy_authentication_handler} handler rather than the couch_httpd_auth version, as couch_httpd is in the process of being deprecated completely. #1476, #1477: The obsolete update_notification feature, which was replaced by /{db}/_changes feeds c. CouchDB 1.2, has been completely removed. This feature never worked in 2.0 for databases, only for shards, making it effectively useless.
2019-09-06 11:10:47 +02:00
couchdb/share/www/dashboard.assets/js/bundle.89dbadd64e69e0df7653.js
couchdb/share/www/dashboard.assets/js/manifest.a154524a560e5f6f431b.js
couchdb/share/www/dashboard.assets/js/vendor.9993972098ce728e0fc2.js
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/share/www/docs/_images/intro-consistency-01.png
couchdb/share/www/docs/_images/intro-consistency-02.png
couchdb/share/www/docs/_images/intro-consistency-03.png
couchdb/share/www/docs/_images/intro-consistency-04.png
couchdb/share/www/docs/_images/intro-consistency-05.png
couchdb/share/www/docs/_images/intro-consistency-06.png
couchdb/share/www/docs/_images/intro-consistency-07.png
couchdb/share/www/docs/_images/intro-why-01.png
couchdb/share/www/docs/_images/intro-why-02.png
couchdb/share/www/docs/_images/intro-why-03.png
couchdb: Upgrade to 2.3.1. Now works with current Erlang. Summary of changes between 2.1.x and 2.3.x are listed below. For a more readable version please see the following URLs: http://docs.couchdb.org/en/latest/whatsnew/2.3.html http://docs.couchdb.org/en/latest/whatsnew/2.2.html http://docs.couchdb.org/en/latest/whatsnew/2.1.html 2.3.x Branch Upgrade Notes #1602: To improve security, there have been major changes in the configuration of query servers, SSL support, and HTTP global handlers: Query servers are NO LONGER DEFINED in the .ini files, and can no longer be altered at run-time. The JavaScript and CoffeeScript query servers continue to be enabled by default. Setup differences have been moved from default.ini to the couchdb and couchdb.cmd start scripts respectively. Additional query servers can now be configured using environment variables: export COUCHDB_QUERY_SERVER_PYTHON="/path/to/python/query/server.py with args" couchdb where the last segment in the environment variable (_PYTHON) matches the usual lowercase(!) query language in the design doc language field (here, python.) Multiple query servers can be configured by using more environment variables. You can also override the default servers if you need to set command- line options (such as couchjs stack size): export COUCHDB_QUERY_SERVER_JAVASCRIPT="/path/to/couchjs /path/to/main.js -S <STACKSIZE>" couchdb The mango query server continues to be enabled by default. The Erlang query server continues to be disabled by default. This change adds a [native_query_servers] enable_erlang_query_server = BOOL setting (defaults to false) to enable the Erlang query server. If the legacy configuration for enabling the query server is detected, that is counted as a true setting as well, so existing configurations continue to work just fine. SSL Support Enabling SSL support in the ini file is now easier: [ssl] enable = true If the legacy httpsd configuration is found in your ini file, this will still enable SSL support, so existing configurations do not need to be changed. HTTP global handlers These are no longer defined in the default.ini file, but have been moved to the couch.app context. If you need to customize your handlers, you can modify the app context using a couchdb.config file as usual. #1602: Also to improve security, the deprecated os_daemons and couch_httpd_proxy functionality has been completely removed ahead of the planned CouchDB 3.0 release. We recommend the use of OS-level daemons such as runit, sysvinit, systemd, upstart, etc. to launch and maintain OS daemons instead, and the use of a reverse proxy server in front of CouchDB (such as haproxy) to proxy access to other services or domains alongside CouchDB. #1543: The node-local (default port 5986) /_restart endpoint has been replaced by the clustered (default port 5984) endpoint /_node/$node/_restart and /_node/_local/_restart endpoints. The node-local endpoint has been removed. #1764: All python scripts shipped with CouchDB, including couchup and the dev/run development cluster script, now specify and require Python 3.x. #1396: CouchDB is now compatible with Erlang 21.x. #1680: The embedded version of rebar used to build CouchDB has been updated to the last version of rebar2 available. This assists in building on non-x86 platforms. #1857: Refuse building with known bad versions of Erlang. 2.2.x Branch Upgrade Notes The minimum supported version of Erlang is now 17, not R16B03. Support for Erlang 21 is still ongoing and will be provided in a future release. The CouchDB replication client can now use the /_session endpoint when authenticating against remote CouchDB instances, improving performance since re-authorization does not have to be performed with every request. Because of this performance improvement, it is recommended to increase the PBKDF2 work factor beyond the default 10 to a modern default such as 10000. This is done via the local ini file setting [couch_httpd_auth] iterations = 10000. Do not do this if an older version of CouchDB is replicating TO this instance or cluster regularly, since CouchDB < 2.2.0 must perform authentication on every request and replication performance will suffer. A future version will make this increased number of iterations a default. #820, #1032: Multiple queries can now be made at the POST /{db}/_all_docs/queries, POST /{db}/_design_docs/queries and POST /{db}/_local_docs/queries endpoints. Also, a new endpoint POST /{db}/_design/{ddoc}/_view/{view}/queries has been introduced to replace the ?queries parameter formerly provided for making multiple queries to a view. The old ?queries parameter is now deprecated and will be removed in a future release of CouchDB. The maximum http request limit, which had been lowered in 2.1.0, has been re-raised to a 4GB limit for now. (#1446). Ongoing discussion about the path forward for future releases is available in #1200 and #1253. #1118: The least recently used (LRU) cache of databases is now only updated on database write, not read. This has lead to significant performance enhancements on very busy clusters. To restore the previous behaviour, your local ini file can contain the block [couchdb] update_lru_on_read = true. #1153: The CouchDB replicator can now make use of the /_session endpoint rather than relying entirely on HTTP basic authentication headers. This can greatly improve replication performance. We encourage you to upgrade any nodes or clusters that regularly act as replication clients to use this new feature, which is enabled by default (#1462). #1283: The [couchdb] enable_database_recovery feature, which only soft-deletes databases in response to a DELETE /{db} call, is now documented in default.ini. #1330: CouchDB externals and OS daemons are now officially deprecated and no longer documented. Support for these features will be completely removed in a future release of CouchDB (probably 3.0.0). #1436: CouchDB proxy authentication now uses a proper chttpd_auth module, simplifying configuration in local ini files. While this is not a backward- compatible breaking change, it is best to update your local ini files to reference the new {chttpd_auth, proxy_authentication_handler} handler rather than the couch_httpd_auth version, as couch_httpd is in the process of being deprecated completely. #1476, #1477: The obsolete update_notification feature, which was replaced by /{db}/_changes feeds c. CouchDB 1.2, has been completely removed. This feature never worked in 2.0 for databases, only for shards, making it effectively useless.
2019-09-06 11:10:47 +02:00
couchdb/share/www/docs/_images/purge-checkpoint-docs.png
Update databases/couchdb to 2.1.1. couchdb 2.1.1 - CouchDB now supports compilation and running under Erlang/OTP 20.x - The couch_peruser functionality is now really fixed - The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customized via the ini file - It is now possible to modify shard maps for system databases - Due to an Erlang bug (ERL-343), invalid paths can be returned if volumes are mounted containing whitespace in their name (fixed) - The current node's local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.- The Dockerfile in the source repository has been retired - Fauxton now uses a version of React with a BSD license. - CouchDB now no longer decompresses documents just to determine their uncompressed size - The design document cache (ddoc_cache) has been rewritten to improve performance - Mango now supports partial indexes - Mango queries can now be paginated - Mango _find accepts an execution_stats parameter - Mango now requires that all of the fields in a candidate index must exist in a query's selector - Other minor improvements. couchdb 2.1.0 - The Mango _find endpoint supports a new combination operator, $allMatch. - New scheduling replicator. - Other minor improvements. See changelog for the 2.1.x branch for more: http://docs.couchdb.org/en/latest/whatsnew/2.1.html
2017-11-07 16:33:27 +01:00
couchdb/share/www/docs/_images/replication-state-diagram.svg
couchdb: Upgrade to 2.3.1. Now works with current Erlang. Summary of changes between 2.1.x and 2.3.x are listed below. For a more readable version please see the following URLs: http://docs.couchdb.org/en/latest/whatsnew/2.3.html http://docs.couchdb.org/en/latest/whatsnew/2.2.html http://docs.couchdb.org/en/latest/whatsnew/2.1.html 2.3.x Branch Upgrade Notes #1602: To improve security, there have been major changes in the configuration of query servers, SSL support, and HTTP global handlers: Query servers are NO LONGER DEFINED in the .ini files, and can no longer be altered at run-time. The JavaScript and CoffeeScript query servers continue to be enabled by default. Setup differences have been moved from default.ini to the couchdb and couchdb.cmd start scripts respectively. Additional query servers can now be configured using environment variables: export COUCHDB_QUERY_SERVER_PYTHON="/path/to/python/query/server.py with args" couchdb where the last segment in the environment variable (_PYTHON) matches the usual lowercase(!) query language in the design doc language field (here, python.) Multiple query servers can be configured by using more environment variables. You can also override the default servers if you need to set command- line options (such as couchjs stack size): export COUCHDB_QUERY_SERVER_JAVASCRIPT="/path/to/couchjs /path/to/main.js -S <STACKSIZE>" couchdb The mango query server continues to be enabled by default. The Erlang query server continues to be disabled by default. This change adds a [native_query_servers] enable_erlang_query_server = BOOL setting (defaults to false) to enable the Erlang query server. If the legacy configuration for enabling the query server is detected, that is counted as a true setting as well, so existing configurations continue to work just fine. SSL Support Enabling SSL support in the ini file is now easier: [ssl] enable = true If the legacy httpsd configuration is found in your ini file, this will still enable SSL support, so existing configurations do not need to be changed. HTTP global handlers These are no longer defined in the default.ini file, but have been moved to the couch.app context. If you need to customize your handlers, you can modify the app context using a couchdb.config file as usual. #1602: Also to improve security, the deprecated os_daemons and couch_httpd_proxy functionality has been completely removed ahead of the planned CouchDB 3.0 release. We recommend the use of OS-level daemons such as runit, sysvinit, systemd, upstart, etc. to launch and maintain OS daemons instead, and the use of a reverse proxy server in front of CouchDB (such as haproxy) to proxy access to other services or domains alongside CouchDB. #1543: The node-local (default port 5986) /_restart endpoint has been replaced by the clustered (default port 5984) endpoint /_node/$node/_restart and /_node/_local/_restart endpoints. The node-local endpoint has been removed. #1764: All python scripts shipped with CouchDB, including couchup and the dev/run development cluster script, now specify and require Python 3.x. #1396: CouchDB is now compatible with Erlang 21.x. #1680: The embedded version of rebar used to build CouchDB has been updated to the last version of rebar2 available. This assists in building on non-x86 platforms. #1857: Refuse building with known bad versions of Erlang. 2.2.x Branch Upgrade Notes The minimum supported version of Erlang is now 17, not R16B03. Support for Erlang 21 is still ongoing and will be provided in a future release. The CouchDB replication client can now use the /_session endpoint when authenticating against remote CouchDB instances, improving performance since re-authorization does not have to be performed with every request. Because of this performance improvement, it is recommended to increase the PBKDF2 work factor beyond the default 10 to a modern default such as 10000. This is done via the local ini file setting [couch_httpd_auth] iterations = 10000. Do not do this if an older version of CouchDB is replicating TO this instance or cluster regularly, since CouchDB < 2.2.0 must perform authentication on every request and replication performance will suffer. A future version will make this increased number of iterations a default. #820, #1032: Multiple queries can now be made at the POST /{db}/_all_docs/queries, POST /{db}/_design_docs/queries and POST /{db}/_local_docs/queries endpoints. Also, a new endpoint POST /{db}/_design/{ddoc}/_view/{view}/queries has been introduced to replace the ?queries parameter formerly provided for making multiple queries to a view. The old ?queries parameter is now deprecated and will be removed in a future release of CouchDB. The maximum http request limit, which had been lowered in 2.1.0, has been re-raised to a 4GB limit for now. (#1446). Ongoing discussion about the path forward for future releases is available in #1200 and #1253. #1118: The least recently used (LRU) cache of databases is now only updated on database write, not read. This has lead to significant performance enhancements on very busy clusters. To restore the previous behaviour, your local ini file can contain the block [couchdb] update_lru_on_read = true. #1153: The CouchDB replicator can now make use of the /_session endpoint rather than relying entirely on HTTP basic authentication headers. This can greatly improve replication performance. We encourage you to upgrade any nodes or clusters that regularly act as replication clients to use this new feature, which is enabled by default (#1462). #1283: The [couchdb] enable_database_recovery feature, which only soft-deletes databases in response to a DELETE /{db} call, is now documented in default.ini. #1330: CouchDB externals and OS daemons are now officially deprecated and no longer documented. Support for these features will be completely removed in a future release of CouchDB (probably 3.0.0). #1436: CouchDB proxy authentication now uses a proper chttpd_auth module, simplifying configuration in local ini files. While this is not a backward- compatible breaking change, it is best to update your local ini files to reference the new {chttpd_auth, proxy_authentication_handler} handler rather than the couch_httpd_auth version, as couch_httpd is in the process of being deprecated completely. #1476, #1477: The obsolete update_notification feature, which was replaced by /{db}/_changes feeds c. CouchDB 1.2, has been completely removed. This feature never worked in 2.0 for databases, only for shards, making it effectively useless.
2019-09-06 11:10:47 +02:00
couchdb/share/www/docs/_images/rev-tree1.png
couchdb/share/www/docs/_images/rev-tree2.png
couchdb/share/www/docs/_images/rev-tree3.png
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/share/www/docs/_images/views-intro-01.png
couchdb/share/www/docs/_images/views-intro-02.png
couchdb/share/www/docs/_images/views-intro-03.png
couchdb/share/www/docs/_images/views-intro-04.png
Update databases/couchdb to 2.1.1. couchdb 2.1.1 - CouchDB now supports compilation and running under Erlang/OTP 20.x - The couch_peruser functionality is now really fixed - The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customized via the ini file - It is now possible to modify shard maps for system databases - Due to an Erlang bug (ERL-343), invalid paths can be returned if volumes are mounted containing whitespace in their name (fixed) - The current node's local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.- The Dockerfile in the source repository has been retired - Fauxton now uses a version of React with a BSD license. - CouchDB now no longer decompresses documents just to determine their uncompressed size - The design document cache (ddoc_cache) has been rewritten to improve performance - Mango now supports partial indexes - Mango queries can now be paginated - Mango _find accepts an execution_stats parameter - Mango now requires that all of the fields in a candidate index must exist in a query's selector - Other minor improvements. couchdb 2.1.0 - The Mango _find endpoint supports a new combination operator, $allMatch. - New scheduling replicator. - Other minor improvements. See changelog for the 2.1.x branch for more: http://docs.couchdb.org/en/latest/whatsnew/2.1.html
2017-11-07 16:33:27 +01:00
couchdb/share/www/docs/_sources/about.rst.txt
couchdb/share/www/docs/_sources/api/basics.rst.txt
couchdb/share/www/docs/_sources/api/database/bulk-api.rst.txt
couchdb/share/www/docs/_sources/api/database/changes.rst.txt
couchdb/share/www/docs/_sources/api/database/common.rst.txt
couchdb/share/www/docs/_sources/api/database/compact.rst.txt
couchdb/share/www/docs/_sources/api/database/find.rst.txt
couchdb/share/www/docs/_sources/api/database/index.rst.txt
couchdb/share/www/docs/_sources/api/database/misc.rst.txt
couchdb/share/www/docs/_sources/api/database/security.rst.txt
couchdb: Upgrade to 2.3.1. Now works with current Erlang. Summary of changes between 2.1.x and 2.3.x are listed below. For a more readable version please see the following URLs: http://docs.couchdb.org/en/latest/whatsnew/2.3.html http://docs.couchdb.org/en/latest/whatsnew/2.2.html http://docs.couchdb.org/en/latest/whatsnew/2.1.html 2.3.x Branch Upgrade Notes #1602: To improve security, there have been major changes in the configuration of query servers, SSL support, and HTTP global handlers: Query servers are NO LONGER DEFINED in the .ini files, and can no longer be altered at run-time. The JavaScript and CoffeeScript query servers continue to be enabled by default. Setup differences have been moved from default.ini to the couchdb and couchdb.cmd start scripts respectively. Additional query servers can now be configured using environment variables: export COUCHDB_QUERY_SERVER_PYTHON="/path/to/python/query/server.py with args" couchdb where the last segment in the environment variable (_PYTHON) matches the usual lowercase(!) query language in the design doc language field (here, python.) Multiple query servers can be configured by using more environment variables. You can also override the default servers if you need to set command- line options (such as couchjs stack size): export COUCHDB_QUERY_SERVER_JAVASCRIPT="/path/to/couchjs /path/to/main.js -S <STACKSIZE>" couchdb The mango query server continues to be enabled by default. The Erlang query server continues to be disabled by default. This change adds a [native_query_servers] enable_erlang_query_server = BOOL setting (defaults to false) to enable the Erlang query server. If the legacy configuration for enabling the query server is detected, that is counted as a true setting as well, so existing configurations continue to work just fine. SSL Support Enabling SSL support in the ini file is now easier: [ssl] enable = true If the legacy httpsd configuration is found in your ini file, this will still enable SSL support, so existing configurations do not need to be changed. HTTP global handlers These are no longer defined in the default.ini file, but have been moved to the couch.app context. If you need to customize your handlers, you can modify the app context using a couchdb.config file as usual. #1602: Also to improve security, the deprecated os_daemons and couch_httpd_proxy functionality has been completely removed ahead of the planned CouchDB 3.0 release. We recommend the use of OS-level daemons such as runit, sysvinit, systemd, upstart, etc. to launch and maintain OS daemons instead, and the use of a reverse proxy server in front of CouchDB (such as haproxy) to proxy access to other services or domains alongside CouchDB. #1543: The node-local (default port 5986) /_restart endpoint has been replaced by the clustered (default port 5984) endpoint /_node/$node/_restart and /_node/_local/_restart endpoints. The node-local endpoint has been removed. #1764: All python scripts shipped with CouchDB, including couchup and the dev/run development cluster script, now specify and require Python 3.x. #1396: CouchDB is now compatible with Erlang 21.x. #1680: The embedded version of rebar used to build CouchDB has been updated to the last version of rebar2 available. This assists in building on non-x86 platforms. #1857: Refuse building with known bad versions of Erlang. 2.2.x Branch Upgrade Notes The minimum supported version of Erlang is now 17, not R16B03. Support for Erlang 21 is still ongoing and will be provided in a future release. The CouchDB replication client can now use the /_session endpoint when authenticating against remote CouchDB instances, improving performance since re-authorization does not have to be performed with every request. Because of this performance improvement, it is recommended to increase the PBKDF2 work factor beyond the default 10 to a modern default such as 10000. This is done via the local ini file setting [couch_httpd_auth] iterations = 10000. Do not do this if an older version of CouchDB is replicating TO this instance or cluster regularly, since CouchDB < 2.2.0 must perform authentication on every request and replication performance will suffer. A future version will make this increased number of iterations a default. #820, #1032: Multiple queries can now be made at the POST /{db}/_all_docs/queries, POST /{db}/_design_docs/queries and POST /{db}/_local_docs/queries endpoints. Also, a new endpoint POST /{db}/_design/{ddoc}/_view/{view}/queries has been introduced to replace the ?queries parameter formerly provided for making multiple queries to a view. The old ?queries parameter is now deprecated and will be removed in a future release of CouchDB. The maximum http request limit, which had been lowered in 2.1.0, has been re-raised to a 4GB limit for now. (#1446). Ongoing discussion about the path forward for future releases is available in #1200 and #1253. #1118: The least recently used (LRU) cache of databases is now only updated on database write, not read. This has lead to significant performance enhancements on very busy clusters. To restore the previous behaviour, your local ini file can contain the block [couchdb] update_lru_on_read = true. #1153: The CouchDB replicator can now make use of the /_session endpoint rather than relying entirely on HTTP basic authentication headers. This can greatly improve replication performance. We encourage you to upgrade any nodes or clusters that regularly act as replication clients to use this new feature, which is enabled by default (#1462). #1283: The [couchdb] enable_database_recovery feature, which only soft-deletes databases in response to a DELETE /{db} call, is now documented in default.ini. #1330: CouchDB externals and OS daemons are now officially deprecated and no longer documented. Support for these features will be completely removed in a future release of CouchDB (probably 3.0.0). #1436: CouchDB proxy authentication now uses a proper chttpd_auth module, simplifying configuration in local ini files. While this is not a backward- compatible breaking change, it is best to update your local ini files to reference the new {chttpd_auth, proxy_authentication_handler} handler rather than the couch_httpd_auth version, as couch_httpd is in the process of being deprecated completely. #1476, #1477: The obsolete update_notification feature, which was replaced by /{db}/_changes feeds c. CouchDB 1.2, has been completely removed. This feature never worked in 2.0 for databases, only for shards, making it effectively useless.
2019-09-06 11:10:47 +02:00
couchdb/share/www/docs/_sources/api/database/shard.rst.txt
Update databases/couchdb to 2.1.1. couchdb 2.1.1 - CouchDB now supports compilation and running under Erlang/OTP 20.x - The couch_peruser functionality is now really fixed - The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customized via the ini file - It is now possible to modify shard maps for system databases - Due to an Erlang bug (ERL-343), invalid paths can be returned if volumes are mounted containing whitespace in their name (fixed) - The current node's local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.- The Dockerfile in the source repository has been retired - Fauxton now uses a version of React with a BSD license. - CouchDB now no longer decompresses documents just to determine their uncompressed size - The design document cache (ddoc_cache) has been rewritten to improve performance - Mango now supports partial indexes - Mango queries can now be paginated - Mango _find accepts an execution_stats parameter - Mango now requires that all of the fields in a candidate index must exist in a query's selector - Other minor improvements. couchdb 2.1.0 - The Mango _find endpoint supports a new combination operator, $allMatch. - New scheduling replicator. - Other minor improvements. See changelog for the 2.1.x branch for more: http://docs.couchdb.org/en/latest/whatsnew/2.1.html
2017-11-07 16:33:27 +01:00
couchdb/share/www/docs/_sources/api/ddoc/common.rst.txt
couchdb/share/www/docs/_sources/api/ddoc/index.rst.txt
couchdb/share/www/docs/_sources/api/ddoc/render.rst.txt
couchdb/share/www/docs/_sources/api/ddoc/rewrites.rst.txt
couchdb/share/www/docs/_sources/api/ddoc/views.rst.txt
couchdb/share/www/docs/_sources/api/document/attachments.rst.txt
couchdb/share/www/docs/_sources/api/document/common.rst.txt
couchdb/share/www/docs/_sources/api/document/index.rst.txt
couchdb/share/www/docs/_sources/api/index.rst.txt
couchdb/share/www/docs/_sources/api/local.rst.txt
couchdb/share/www/docs/_sources/api/server/authn.rst.txt
couchdb/share/www/docs/_sources/api/server/common.rst.txt
couchdb/share/www/docs/_sources/api/server/configuration.rst.txt
couchdb/share/www/docs/_sources/api/server/index.rst.txt
couchdb: Upgrade to 2.3.1. Now works with current Erlang. Summary of changes between 2.1.x and 2.3.x are listed below. For a more readable version please see the following URLs: http://docs.couchdb.org/en/latest/whatsnew/2.3.html http://docs.couchdb.org/en/latest/whatsnew/2.2.html http://docs.couchdb.org/en/latest/whatsnew/2.1.html 2.3.x Branch Upgrade Notes #1602: To improve security, there have been major changes in the configuration of query servers, SSL support, and HTTP global handlers: Query servers are NO LONGER DEFINED in the .ini files, and can no longer be altered at run-time. The JavaScript and CoffeeScript query servers continue to be enabled by default. Setup differences have been moved from default.ini to the couchdb and couchdb.cmd start scripts respectively. Additional query servers can now be configured using environment variables: export COUCHDB_QUERY_SERVER_PYTHON="/path/to/python/query/server.py with args" couchdb where the last segment in the environment variable (_PYTHON) matches the usual lowercase(!) query language in the design doc language field (here, python.) Multiple query servers can be configured by using more environment variables. You can also override the default servers if you need to set command- line options (such as couchjs stack size): export COUCHDB_QUERY_SERVER_JAVASCRIPT="/path/to/couchjs /path/to/main.js -S <STACKSIZE>" couchdb The mango query server continues to be enabled by default. The Erlang query server continues to be disabled by default. This change adds a [native_query_servers] enable_erlang_query_server = BOOL setting (defaults to false) to enable the Erlang query server. If the legacy configuration for enabling the query server is detected, that is counted as a true setting as well, so existing configurations continue to work just fine. SSL Support Enabling SSL support in the ini file is now easier: [ssl] enable = true If the legacy httpsd configuration is found in your ini file, this will still enable SSL support, so existing configurations do not need to be changed. HTTP global handlers These are no longer defined in the default.ini file, but have been moved to the couch.app context. If you need to customize your handlers, you can modify the app context using a couchdb.config file as usual. #1602: Also to improve security, the deprecated os_daemons and couch_httpd_proxy functionality has been completely removed ahead of the planned CouchDB 3.0 release. We recommend the use of OS-level daemons such as runit, sysvinit, systemd, upstart, etc. to launch and maintain OS daemons instead, and the use of a reverse proxy server in front of CouchDB (such as haproxy) to proxy access to other services or domains alongside CouchDB. #1543: The node-local (default port 5986) /_restart endpoint has been replaced by the clustered (default port 5984) endpoint /_node/$node/_restart and /_node/_local/_restart endpoints. The node-local endpoint has been removed. #1764: All python scripts shipped with CouchDB, including couchup and the dev/run development cluster script, now specify and require Python 3.x. #1396: CouchDB is now compatible with Erlang 21.x. #1680: The embedded version of rebar used to build CouchDB has been updated to the last version of rebar2 available. This assists in building on non-x86 platforms. #1857: Refuse building with known bad versions of Erlang. 2.2.x Branch Upgrade Notes The minimum supported version of Erlang is now 17, not R16B03. Support for Erlang 21 is still ongoing and will be provided in a future release. The CouchDB replication client can now use the /_session endpoint when authenticating against remote CouchDB instances, improving performance since re-authorization does not have to be performed with every request. Because of this performance improvement, it is recommended to increase the PBKDF2 work factor beyond the default 10 to a modern default such as 10000. This is done via the local ini file setting [couch_httpd_auth] iterations = 10000. Do not do this if an older version of CouchDB is replicating TO this instance or cluster regularly, since CouchDB < 2.2.0 must perform authentication on every request and replication performance will suffer. A future version will make this increased number of iterations a default. #820, #1032: Multiple queries can now be made at the POST /{db}/_all_docs/queries, POST /{db}/_design_docs/queries and POST /{db}/_local_docs/queries endpoints. Also, a new endpoint POST /{db}/_design/{ddoc}/_view/{view}/queries has been introduced to replace the ?queries parameter formerly provided for making multiple queries to a view. The old ?queries parameter is now deprecated and will be removed in a future release of CouchDB. The maximum http request limit, which had been lowered in 2.1.0, has been re-raised to a 4GB limit for now. (#1446). Ongoing discussion about the path forward for future releases is available in #1200 and #1253. #1118: The least recently used (LRU) cache of databases is now only updated on database write, not read. This has lead to significant performance enhancements on very busy clusters. To restore the previous behaviour, your local ini file can contain the block [couchdb] update_lru_on_read = true. #1153: The CouchDB replicator can now make use of the /_session endpoint rather than relying entirely on HTTP basic authentication headers. This can greatly improve replication performance. We encourage you to upgrade any nodes or clusters that regularly act as replication clients to use this new feature, which is enabled by default (#1462). #1283: The [couchdb] enable_database_recovery feature, which only soft-deletes databases in response to a DELETE /{db} call, is now documented in default.ini. #1330: CouchDB externals and OS daemons are now officially deprecated and no longer documented. Support for these features will be completely removed in a future release of CouchDB (probably 3.0.0). #1436: CouchDB proxy authentication now uses a proper chttpd_auth module, simplifying configuration in local ini files. While this is not a backward- compatible breaking change, it is best to update your local ini files to reference the new {chttpd_auth, proxy_authentication_handler} handler rather than the couch_httpd_auth version, as couch_httpd is in the process of being deprecated completely. #1476, #1477: The obsolete update_notification feature, which was replaced by /{db}/_changes feeds c. CouchDB 1.2, has been completely removed. This feature never worked in 2.0 for databases, only for shards, making it effectively useless.
2019-09-06 11:10:47 +02:00
couchdb/share/www/docs/_sources/best-practices/documents.rst.txt
couchdb/share/www/docs/_sources/best-practices/forms.rst.txt
couchdb/share/www/docs/_sources/best-practices/index.rst.txt
couchdb/share/www/docs/_sources/best-practices/iso-date.rst.txt
couchdb/share/www/docs/_sources/best-practices/jsdevel.rst.txt
couchdb/share/www/docs/_sources/best-practices/reverse-proxies.rst.txt
couchdb/share/www/docs/_sources/best-practices/views.rst.txt
Update databases/couchdb to 2.1.1. couchdb 2.1.1 - CouchDB now supports compilation and running under Erlang/OTP 20.x - The couch_peruser functionality is now really fixed - The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customized via the ini file - It is now possible to modify shard maps for system databases - Due to an Erlang bug (ERL-343), invalid paths can be returned if volumes are mounted containing whitespace in their name (fixed) - The current node's local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.- The Dockerfile in the source repository has been retired - Fauxton now uses a version of React with a BSD license. - CouchDB now no longer decompresses documents just to determine their uncompressed size - The design document cache (ddoc_cache) has been rewritten to improve performance - Mango now supports partial indexes - Mango queries can now be paginated - Mango _find accepts an execution_stats parameter - Mango now requires that all of the fields in a candidate index must exist in a query's selector - Other minor improvements. couchdb 2.1.0 - The Mango _find endpoint supports a new combination operator, $allMatch. - New scheduling replicator. - Other minor improvements. See changelog for the 2.1.x branch for more: http://docs.couchdb.org/en/latest/whatsnew/2.1.html
2017-11-07 16:33:27 +01:00
couchdb/share/www/docs/_sources/cluster/databases.rst.txt
couchdb/share/www/docs/_sources/cluster/index.rst.txt
couchdb/share/www/docs/_sources/cluster/nodes.rst.txt
couchdb: Upgrade to 2.3.1. Now works with current Erlang. Summary of changes between 2.1.x and 2.3.x are listed below. For a more readable version please see the following URLs: http://docs.couchdb.org/en/latest/whatsnew/2.3.html http://docs.couchdb.org/en/latest/whatsnew/2.2.html http://docs.couchdb.org/en/latest/whatsnew/2.1.html 2.3.x Branch Upgrade Notes #1602: To improve security, there have been major changes in the configuration of query servers, SSL support, and HTTP global handlers: Query servers are NO LONGER DEFINED in the .ini files, and can no longer be altered at run-time. The JavaScript and CoffeeScript query servers continue to be enabled by default. Setup differences have been moved from default.ini to the couchdb and couchdb.cmd start scripts respectively. Additional query servers can now be configured using environment variables: export COUCHDB_QUERY_SERVER_PYTHON="/path/to/python/query/server.py with args" couchdb where the last segment in the environment variable (_PYTHON) matches the usual lowercase(!) query language in the design doc language field (here, python.) Multiple query servers can be configured by using more environment variables. You can also override the default servers if you need to set command- line options (such as couchjs stack size): export COUCHDB_QUERY_SERVER_JAVASCRIPT="/path/to/couchjs /path/to/main.js -S <STACKSIZE>" couchdb The mango query server continues to be enabled by default. The Erlang query server continues to be disabled by default. This change adds a [native_query_servers] enable_erlang_query_server = BOOL setting (defaults to false) to enable the Erlang query server. If the legacy configuration for enabling the query server is detected, that is counted as a true setting as well, so existing configurations continue to work just fine. SSL Support Enabling SSL support in the ini file is now easier: [ssl] enable = true If the legacy httpsd configuration is found in your ini file, this will still enable SSL support, so existing configurations do not need to be changed. HTTP global handlers These are no longer defined in the default.ini file, but have been moved to the couch.app context. If you need to customize your handlers, you can modify the app context using a couchdb.config file as usual. #1602: Also to improve security, the deprecated os_daemons and couch_httpd_proxy functionality has been completely removed ahead of the planned CouchDB 3.0 release. We recommend the use of OS-level daemons such as runit, sysvinit, systemd, upstart, etc. to launch and maintain OS daemons instead, and the use of a reverse proxy server in front of CouchDB (such as haproxy) to proxy access to other services or domains alongside CouchDB. #1543: The node-local (default port 5986) /_restart endpoint has been replaced by the clustered (default port 5984) endpoint /_node/$node/_restart and /_node/_local/_restart endpoints. The node-local endpoint has been removed. #1764: All python scripts shipped with CouchDB, including couchup and the dev/run development cluster script, now specify and require Python 3.x. #1396: CouchDB is now compatible with Erlang 21.x. #1680: The embedded version of rebar used to build CouchDB has been updated to the last version of rebar2 available. This assists in building on non-x86 platforms. #1857: Refuse building with known bad versions of Erlang. 2.2.x Branch Upgrade Notes The minimum supported version of Erlang is now 17, not R16B03. Support for Erlang 21 is still ongoing and will be provided in a future release. The CouchDB replication client can now use the /_session endpoint when authenticating against remote CouchDB instances, improving performance since re-authorization does not have to be performed with every request. Because of this performance improvement, it is recommended to increase the PBKDF2 work factor beyond the default 10 to a modern default such as 10000. This is done via the local ini file setting [couch_httpd_auth] iterations = 10000. Do not do this if an older version of CouchDB is replicating TO this instance or cluster regularly, since CouchDB < 2.2.0 must perform authentication on every request and replication performance will suffer. A future version will make this increased number of iterations a default. #820, #1032: Multiple queries can now be made at the POST /{db}/_all_docs/queries, POST /{db}/_design_docs/queries and POST /{db}/_local_docs/queries endpoints. Also, a new endpoint POST /{db}/_design/{ddoc}/_view/{view}/queries has been introduced to replace the ?queries parameter formerly provided for making multiple queries to a view. The old ?queries parameter is now deprecated and will be removed in a future release of CouchDB. The maximum http request limit, which had been lowered in 2.1.0, has been re-raised to a 4GB limit for now. (#1446). Ongoing discussion about the path forward for future releases is available in #1200 and #1253. #1118: The least recently used (LRU) cache of databases is now only updated on database write, not read. This has lead to significant performance enhancements on very busy clusters. To restore the previous behaviour, your local ini file can contain the block [couchdb] update_lru_on_read = true. #1153: The CouchDB replicator can now make use of the /_session endpoint rather than relying entirely on HTTP basic authentication headers. This can greatly improve replication performance. We encourage you to upgrade any nodes or clusters that regularly act as replication clients to use this new feature, which is enabled by default (#1462). #1283: The [couchdb] enable_database_recovery feature, which only soft-deletes databases in response to a DELETE /{db} call, is now documented in default.ini. #1330: CouchDB externals and OS daemons are now officially deprecated and no longer documented. Support for these features will be completely removed in a future release of CouchDB (probably 3.0.0). #1436: CouchDB proxy authentication now uses a proper chttpd_auth module, simplifying configuration in local ini files. While this is not a backward- compatible breaking change, it is best to update your local ini files to reference the new {chttpd_auth, proxy_authentication_handler} handler rather than the couch_httpd_auth version, as couch_httpd is in the process of being deprecated completely. #1476, #1477: The obsolete update_notification feature, which was replaced by /{db}/_changes feeds c. CouchDB 1.2, has been completely removed. This feature never worked in 2.0 for databases, only for shards, making it effectively useless.
2019-09-06 11:10:47 +02:00
couchdb/share/www/docs/_sources/cluster/purging.rst.txt
Update databases/couchdb to 2.1.1. couchdb 2.1.1 - CouchDB now supports compilation and running under Erlang/OTP 20.x - The couch_peruser functionality is now really fixed - The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customized via the ini file - It is now possible to modify shard maps for system databases - Due to an Erlang bug (ERL-343), invalid paths can be returned if volumes are mounted containing whitespace in their name (fixed) - The current node's local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.- The Dockerfile in the source repository has been retired - Fauxton now uses a version of React with a BSD license. - CouchDB now no longer decompresses documents just to determine their uncompressed size - The design document cache (ddoc_cache) has been rewritten to improve performance - Mango now supports partial indexes - Mango queries can now be paginated - Mango _find accepts an execution_stats parameter - Mango now requires that all of the fields in a candidate index must exist in a query's selector - Other minor improvements. couchdb 2.1.0 - The Mango _find endpoint supports a new combination operator, $allMatch. - New scheduling replicator. - Other minor improvements. See changelog for the 2.1.x branch for more: http://docs.couchdb.org/en/latest/whatsnew/2.1.html
2017-11-07 16:33:27 +01:00
couchdb/share/www/docs/_sources/cluster/sharding.rst.txt
couchdb/share/www/docs/_sources/cluster/theory.rst.txt
couchdb/share/www/docs/_sources/config/auth.rst.txt
couchdb/share/www/docs/_sources/config/cluster.rst.txt
couchdb/share/www/docs/_sources/config/compaction.rst.txt
couchdb/share/www/docs/_sources/config/couch-peruser.rst.txt
couchdb/share/www/docs/_sources/config/couchdb.rst.txt
couchdb/share/www/docs/_sources/config/http.rst.txt
couchdb/share/www/docs/_sources/config/index.rst.txt
couchdb/share/www/docs/_sources/config/intro.rst.txt
couchdb/share/www/docs/_sources/config/logging.rst.txt
couchdb/share/www/docs/_sources/config/misc.rst.txt
couchdb/share/www/docs/_sources/config/query-servers.rst.txt
couchdb/share/www/docs/_sources/config/replicator.rst.txt
couchdb/share/www/docs/_sources/config/services.rst.txt
couchdb/share/www/docs/_sources/contributing.rst.txt
couchdb/share/www/docs/_sources/cve/2010-0009.rst.txt
couchdb/share/www/docs/_sources/cve/2010-2234.rst.txt
couchdb/share/www/docs/_sources/cve/2010-3854.rst.txt
couchdb/share/www/docs/_sources/cve/2012-5641.rst.txt
couchdb/share/www/docs/_sources/cve/2012-5649.rst.txt
couchdb/share/www/docs/_sources/cve/2012-5650.rst.txt
couchdb/share/www/docs/_sources/cve/2014-2668.rst.txt
couchdb: Upgrade to 2.3.1. Now works with current Erlang. Summary of changes between 2.1.x and 2.3.x are listed below. For a more readable version please see the following URLs: http://docs.couchdb.org/en/latest/whatsnew/2.3.html http://docs.couchdb.org/en/latest/whatsnew/2.2.html http://docs.couchdb.org/en/latest/whatsnew/2.1.html 2.3.x Branch Upgrade Notes #1602: To improve security, there have been major changes in the configuration of query servers, SSL support, and HTTP global handlers: Query servers are NO LONGER DEFINED in the .ini files, and can no longer be altered at run-time. The JavaScript and CoffeeScript query servers continue to be enabled by default. Setup differences have been moved from default.ini to the couchdb and couchdb.cmd start scripts respectively. Additional query servers can now be configured using environment variables: export COUCHDB_QUERY_SERVER_PYTHON="/path/to/python/query/server.py with args" couchdb where the last segment in the environment variable (_PYTHON) matches the usual lowercase(!) query language in the design doc language field (here, python.) Multiple query servers can be configured by using more environment variables. You can also override the default servers if you need to set command- line options (such as couchjs stack size): export COUCHDB_QUERY_SERVER_JAVASCRIPT="/path/to/couchjs /path/to/main.js -S <STACKSIZE>" couchdb The mango query server continues to be enabled by default. The Erlang query server continues to be disabled by default. This change adds a [native_query_servers] enable_erlang_query_server = BOOL setting (defaults to false) to enable the Erlang query server. If the legacy configuration for enabling the query server is detected, that is counted as a true setting as well, so existing configurations continue to work just fine. SSL Support Enabling SSL support in the ini file is now easier: [ssl] enable = true If the legacy httpsd configuration is found in your ini file, this will still enable SSL support, so existing configurations do not need to be changed. HTTP global handlers These are no longer defined in the default.ini file, but have been moved to the couch.app context. If you need to customize your handlers, you can modify the app context using a couchdb.config file as usual. #1602: Also to improve security, the deprecated os_daemons and couch_httpd_proxy functionality has been completely removed ahead of the planned CouchDB 3.0 release. We recommend the use of OS-level daemons such as runit, sysvinit, systemd, upstart, etc. to launch and maintain OS daemons instead, and the use of a reverse proxy server in front of CouchDB (such as haproxy) to proxy access to other services or domains alongside CouchDB. #1543: The node-local (default port 5986) /_restart endpoint has been replaced by the clustered (default port 5984) endpoint /_node/$node/_restart and /_node/_local/_restart endpoints. The node-local endpoint has been removed. #1764: All python scripts shipped with CouchDB, including couchup and the dev/run development cluster script, now specify and require Python 3.x. #1396: CouchDB is now compatible with Erlang 21.x. #1680: The embedded version of rebar used to build CouchDB has been updated to the last version of rebar2 available. This assists in building on non-x86 platforms. #1857: Refuse building with known bad versions of Erlang. 2.2.x Branch Upgrade Notes The minimum supported version of Erlang is now 17, not R16B03. Support for Erlang 21 is still ongoing and will be provided in a future release. The CouchDB replication client can now use the /_session endpoint when authenticating against remote CouchDB instances, improving performance since re-authorization does not have to be performed with every request. Because of this performance improvement, it is recommended to increase the PBKDF2 work factor beyond the default 10 to a modern default such as 10000. This is done via the local ini file setting [couch_httpd_auth] iterations = 10000. Do not do this if an older version of CouchDB is replicating TO this instance or cluster regularly, since CouchDB < 2.2.0 must perform authentication on every request and replication performance will suffer. A future version will make this increased number of iterations a default. #820, #1032: Multiple queries can now be made at the POST /{db}/_all_docs/queries, POST /{db}/_design_docs/queries and POST /{db}/_local_docs/queries endpoints. Also, a new endpoint POST /{db}/_design/{ddoc}/_view/{view}/queries has been introduced to replace the ?queries parameter formerly provided for making multiple queries to a view. The old ?queries parameter is now deprecated and will be removed in a future release of CouchDB. The maximum http request limit, which had been lowered in 2.1.0, has been re-raised to a 4GB limit for now. (#1446). Ongoing discussion about the path forward for future releases is available in #1200 and #1253. #1118: The least recently used (LRU) cache of databases is now only updated on database write, not read. This has lead to significant performance enhancements on very busy clusters. To restore the previous behaviour, your local ini file can contain the block [couchdb] update_lru_on_read = true. #1153: The CouchDB replicator can now make use of the /_session endpoint rather than relying entirely on HTTP basic authentication headers. This can greatly improve replication performance. We encourage you to upgrade any nodes or clusters that regularly act as replication clients to use this new feature, which is enabled by default (#1462). #1283: The [couchdb] enable_database_recovery feature, which only soft-deletes databases in response to a DELETE /{db} call, is now documented in default.ini. #1330: CouchDB externals and OS daemons are now officially deprecated and no longer documented. Support for these features will be completely removed in a future release of CouchDB (probably 3.0.0). #1436: CouchDB proxy authentication now uses a proper chttpd_auth module, simplifying configuration in local ini files. While this is not a backward- compatible breaking change, it is best to update your local ini files to reference the new {chttpd_auth, proxy_authentication_handler} handler rather than the couch_httpd_auth version, as couch_httpd is in the process of being deprecated completely. #1476, #1477: The obsolete update_notification feature, which was replaced by /{db}/_changes feeds c. CouchDB 1.2, has been completely removed. This feature never worked in 2.0 for databases, only for shards, making it effectively useless.
2019-09-06 11:10:47 +02:00
couchdb/share/www/docs/_sources/cve/2017-12635.rst.txt
couchdb/share/www/docs/_sources/cve/2017-12636.rst.txt
couchdb/share/www/docs/_sources/cve/2018-11769.rst.txt
couchdb/share/www/docs/_sources/cve/2018-17188.rst.txt
couchdb/share/www/docs/_sources/cve/2018-8007.rst.txt
Update databases/couchdb to 2.1.1. couchdb 2.1.1 - CouchDB now supports compilation and running under Erlang/OTP 20.x - The couch_peruser functionality is now really fixed - The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customized via the ini file - It is now possible to modify shard maps for system databases - Due to an Erlang bug (ERL-343), invalid paths can be returned if volumes are mounted containing whitespace in their name (fixed) - The current node's local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.- The Dockerfile in the source repository has been retired - Fauxton now uses a version of React with a BSD license. - CouchDB now no longer decompresses documents just to determine their uncompressed size - The design document cache (ddoc_cache) has been rewritten to improve performance - Mango now supports partial indexes - Mango queries can now be paginated - Mango _find accepts an execution_stats parameter - Mango now requires that all of the fields in a candidate index must exist in a query's selector - Other minor improvements. couchdb 2.1.0 - The Mango _find endpoint supports a new combination operator, $allMatch. - New scheduling replicator. - Other minor improvements. See changelog for the 2.1.x branch for more: http://docs.couchdb.org/en/latest/whatsnew/2.1.html
2017-11-07 16:33:27 +01:00
couchdb/share/www/docs/_sources/cve/index.rst.txt
couchdb/share/www/docs/_sources/ddocs/ddocs.rst.txt
couchdb/share/www/docs/_sources/ddocs/index.rst.txt
couchdb/share/www/docs/_sources/ddocs/views/collation.rst.txt
couchdb/share/www/docs/_sources/ddocs/views/index.rst.txt
couchdb/share/www/docs/_sources/ddocs/views/intro.rst.txt
couchdb/share/www/docs/_sources/ddocs/views/joins.rst.txt
couchdb/share/www/docs/_sources/ddocs/views/nosql.rst.txt
couchdb/share/www/docs/_sources/ddocs/views/pagination.rst.txt
couchdb/share/www/docs/_sources/experimental.rst.txt
couchdb/share/www/docs/_sources/fauxton/index.rst.txt
couchdb/share/www/docs/_sources/fauxton/install.rst.txt
couchdb/share/www/docs/_sources/index.rst.txt
couchdb/share/www/docs/_sources/install/docker.rst.txt
couchdb/share/www/docs/_sources/install/freebsd.rst.txt
couchdb/share/www/docs/_sources/install/index.rst.txt
couchdb/share/www/docs/_sources/install/mac.rst.txt
couchdb/share/www/docs/_sources/install/snap.rst.txt
couchdb/share/www/docs/_sources/install/troubleshooting.rst.txt
couchdb/share/www/docs/_sources/install/unix.rst.txt
couchdb/share/www/docs/_sources/install/upgrading.rst.txt
couchdb/share/www/docs/_sources/install/windows.rst.txt
couchdb/share/www/docs/_sources/intro/api.rst.txt
couchdb/share/www/docs/_sources/intro/consistency.rst.txt
couchdb/share/www/docs/_sources/intro/curl.rst.txt
couchdb/share/www/docs/_sources/intro/index.rst.txt
couchdb/share/www/docs/_sources/intro/overview.rst.txt
couchdb/share/www/docs/_sources/intro/security.rst.txt
couchdb/share/www/docs/_sources/intro/tour.rst.txt
couchdb/share/www/docs/_sources/intro/why.rst.txt
couchdb/share/www/docs/_sources/json-structure.rst.txt
couchdb: Upgrade to 2.3.1. Now works with current Erlang. Summary of changes between 2.1.x and 2.3.x are listed below. For a more readable version please see the following URLs: http://docs.couchdb.org/en/latest/whatsnew/2.3.html http://docs.couchdb.org/en/latest/whatsnew/2.2.html http://docs.couchdb.org/en/latest/whatsnew/2.1.html 2.3.x Branch Upgrade Notes #1602: To improve security, there have been major changes in the configuration of query servers, SSL support, and HTTP global handlers: Query servers are NO LONGER DEFINED in the .ini files, and can no longer be altered at run-time. The JavaScript and CoffeeScript query servers continue to be enabled by default. Setup differences have been moved from default.ini to the couchdb and couchdb.cmd start scripts respectively. Additional query servers can now be configured using environment variables: export COUCHDB_QUERY_SERVER_PYTHON="/path/to/python/query/server.py with args" couchdb where the last segment in the environment variable (_PYTHON) matches the usual lowercase(!) query language in the design doc language field (here, python.) Multiple query servers can be configured by using more environment variables. You can also override the default servers if you need to set command- line options (such as couchjs stack size): export COUCHDB_QUERY_SERVER_JAVASCRIPT="/path/to/couchjs /path/to/main.js -S <STACKSIZE>" couchdb The mango query server continues to be enabled by default. The Erlang query server continues to be disabled by default. This change adds a [native_query_servers] enable_erlang_query_server = BOOL setting (defaults to false) to enable the Erlang query server. If the legacy configuration for enabling the query server is detected, that is counted as a true setting as well, so existing configurations continue to work just fine. SSL Support Enabling SSL support in the ini file is now easier: [ssl] enable = true If the legacy httpsd configuration is found in your ini file, this will still enable SSL support, so existing configurations do not need to be changed. HTTP global handlers These are no longer defined in the default.ini file, but have been moved to the couch.app context. If you need to customize your handlers, you can modify the app context using a couchdb.config file as usual. #1602: Also to improve security, the deprecated os_daemons and couch_httpd_proxy functionality has been completely removed ahead of the planned CouchDB 3.0 release. We recommend the use of OS-level daemons such as runit, sysvinit, systemd, upstart, etc. to launch and maintain OS daemons instead, and the use of a reverse proxy server in front of CouchDB (such as haproxy) to proxy access to other services or domains alongside CouchDB. #1543: The node-local (default port 5986) /_restart endpoint has been replaced by the clustered (default port 5984) endpoint /_node/$node/_restart and /_node/_local/_restart endpoints. The node-local endpoint has been removed. #1764: All python scripts shipped with CouchDB, including couchup and the dev/run development cluster script, now specify and require Python 3.x. #1396: CouchDB is now compatible with Erlang 21.x. #1680: The embedded version of rebar used to build CouchDB has been updated to the last version of rebar2 available. This assists in building on non-x86 platforms. #1857: Refuse building with known bad versions of Erlang. 2.2.x Branch Upgrade Notes The minimum supported version of Erlang is now 17, not R16B03. Support for Erlang 21 is still ongoing and will be provided in a future release. The CouchDB replication client can now use the /_session endpoint when authenticating against remote CouchDB instances, improving performance since re-authorization does not have to be performed with every request. Because of this performance improvement, it is recommended to increase the PBKDF2 work factor beyond the default 10 to a modern default such as 10000. This is done via the local ini file setting [couch_httpd_auth] iterations = 10000. Do not do this if an older version of CouchDB is replicating TO this instance or cluster regularly, since CouchDB < 2.2.0 must perform authentication on every request and replication performance will suffer. A future version will make this increased number of iterations a default. #820, #1032: Multiple queries can now be made at the POST /{db}/_all_docs/queries, POST /{db}/_design_docs/queries and POST /{db}/_local_docs/queries endpoints. Also, a new endpoint POST /{db}/_design/{ddoc}/_view/{view}/queries has been introduced to replace the ?queries parameter formerly provided for making multiple queries to a view. The old ?queries parameter is now deprecated and will be removed in a future release of CouchDB. The maximum http request limit, which had been lowered in 2.1.0, has been re-raised to a 4GB limit for now. (#1446). Ongoing discussion about the path forward for future releases is available in #1200 and #1253. #1118: The least recently used (LRU) cache of databases is now only updated on database write, not read. This has lead to significant performance enhancements on very busy clusters. To restore the previous behaviour, your local ini file can contain the block [couchdb] update_lru_on_read = true. #1153: The CouchDB replicator can now make use of the /_session endpoint rather than relying entirely on HTTP basic authentication headers. This can greatly improve replication performance. We encourage you to upgrade any nodes or clusters that regularly act as replication clients to use this new feature, which is enabled by default (#1462). #1283: The [couchdb] enable_database_recovery feature, which only soft-deletes databases in response to a DELETE /{db} call, is now documented in default.ini. #1330: CouchDB externals and OS daemons are now officially deprecated and no longer documented. Support for these features will be completely removed in a future release of CouchDB (probably 3.0.0). #1436: CouchDB proxy authentication now uses a proper chttpd_auth module, simplifying configuration in local ini files. While this is not a backward- compatible breaking change, it is best to update your local ini files to reference the new {chttpd_auth, proxy_authentication_handler} handler rather than the couch_httpd_auth version, as couch_httpd is in the process of being deprecated completely. #1476, #1477: The obsolete update_notification feature, which was replaced by /{db}/_changes feeds c. CouchDB 1.2, has been completely removed. This feature never worked in 2.0 for databases, only for shards, making it effectively useless.
2019-09-06 11:10:47 +02:00
couchdb/share/www/docs/_sources/maintenance/backups.rst.txt
Update databases/couchdb to 2.1.1. couchdb 2.1.1 - CouchDB now supports compilation and running under Erlang/OTP 20.x - The couch_peruser functionality is now really fixed - The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customized via the ini file - It is now possible to modify shard maps for system databases - Due to an Erlang bug (ERL-343), invalid paths can be returned if volumes are mounted containing whitespace in their name (fixed) - The current node's local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.- The Dockerfile in the source repository has been retired - Fauxton now uses a version of React with a BSD license. - CouchDB now no longer decompresses documents just to determine their uncompressed size - The design document cache (ddoc_cache) has been rewritten to improve performance - Mango now supports partial indexes - Mango queries can now be paginated - Mango _find accepts an execution_stats parameter - Mango now requires that all of the fields in a candidate index must exist in a query's selector - Other minor improvements. couchdb 2.1.0 - The Mango _find endpoint supports a new combination operator, $allMatch. - New scheduling replicator. - Other minor improvements. See changelog for the 2.1.x branch for more: http://docs.couchdb.org/en/latest/whatsnew/2.1.html
2017-11-07 16:33:27 +01:00
couchdb/share/www/docs/_sources/maintenance/compaction.rst.txt
couchdb/share/www/docs/_sources/maintenance/index.rst.txt
couchdb/share/www/docs/_sources/maintenance/performance.rst.txt
couchdb/share/www/docs/_sources/query-server/erlang.rst.txt
couchdb/share/www/docs/_sources/query-server/index.rst.txt
couchdb/share/www/docs/_sources/query-server/javascript.rst.txt
couchdb/share/www/docs/_sources/query-server/protocol.rst.txt
couchdb/share/www/docs/_sources/replication/conflicts.rst.txt
couchdb/share/www/docs/_sources/replication/index.rst.txt
couchdb/share/www/docs/_sources/replication/intro.rst.txt
couchdb/share/www/docs/_sources/replication/protocol.rst.txt
couchdb/share/www/docs/_sources/replication/replicator.rst.txt
couchdb: Upgrade to 2.3.1. Now works with current Erlang. Summary of changes between 2.1.x and 2.3.x are listed below. For a more readable version please see the following URLs: http://docs.couchdb.org/en/latest/whatsnew/2.3.html http://docs.couchdb.org/en/latest/whatsnew/2.2.html http://docs.couchdb.org/en/latest/whatsnew/2.1.html 2.3.x Branch Upgrade Notes #1602: To improve security, there have been major changes in the configuration of query servers, SSL support, and HTTP global handlers: Query servers are NO LONGER DEFINED in the .ini files, and can no longer be altered at run-time. The JavaScript and CoffeeScript query servers continue to be enabled by default. Setup differences have been moved from default.ini to the couchdb and couchdb.cmd start scripts respectively. Additional query servers can now be configured using environment variables: export COUCHDB_QUERY_SERVER_PYTHON="/path/to/python/query/server.py with args" couchdb where the last segment in the environment variable (_PYTHON) matches the usual lowercase(!) query language in the design doc language field (here, python.) Multiple query servers can be configured by using more environment variables. You can also override the default servers if you need to set command- line options (such as couchjs stack size): export COUCHDB_QUERY_SERVER_JAVASCRIPT="/path/to/couchjs /path/to/main.js -S <STACKSIZE>" couchdb The mango query server continues to be enabled by default. The Erlang query server continues to be disabled by default. This change adds a [native_query_servers] enable_erlang_query_server = BOOL setting (defaults to false) to enable the Erlang query server. If the legacy configuration for enabling the query server is detected, that is counted as a true setting as well, so existing configurations continue to work just fine. SSL Support Enabling SSL support in the ini file is now easier: [ssl] enable = true If the legacy httpsd configuration is found in your ini file, this will still enable SSL support, so existing configurations do not need to be changed. HTTP global handlers These are no longer defined in the default.ini file, but have been moved to the couch.app context. If you need to customize your handlers, you can modify the app context using a couchdb.config file as usual. #1602: Also to improve security, the deprecated os_daemons and couch_httpd_proxy functionality has been completely removed ahead of the planned CouchDB 3.0 release. We recommend the use of OS-level daemons such as runit, sysvinit, systemd, upstart, etc. to launch and maintain OS daemons instead, and the use of a reverse proxy server in front of CouchDB (such as haproxy) to proxy access to other services or domains alongside CouchDB. #1543: The node-local (default port 5986) /_restart endpoint has been replaced by the clustered (default port 5984) endpoint /_node/$node/_restart and /_node/_local/_restart endpoints. The node-local endpoint has been removed. #1764: All python scripts shipped with CouchDB, including couchup and the dev/run development cluster script, now specify and require Python 3.x. #1396: CouchDB is now compatible with Erlang 21.x. #1680: The embedded version of rebar used to build CouchDB has been updated to the last version of rebar2 available. This assists in building on non-x86 platforms. #1857: Refuse building with known bad versions of Erlang. 2.2.x Branch Upgrade Notes The minimum supported version of Erlang is now 17, not R16B03. Support for Erlang 21 is still ongoing and will be provided in a future release. The CouchDB replication client can now use the /_session endpoint when authenticating against remote CouchDB instances, improving performance since re-authorization does not have to be performed with every request. Because of this performance improvement, it is recommended to increase the PBKDF2 work factor beyond the default 10 to a modern default such as 10000. This is done via the local ini file setting [couch_httpd_auth] iterations = 10000. Do not do this if an older version of CouchDB is replicating TO this instance or cluster regularly, since CouchDB < 2.2.0 must perform authentication on every request and replication performance will suffer. A future version will make this increased number of iterations a default. #820, #1032: Multiple queries can now be made at the POST /{db}/_all_docs/queries, POST /{db}/_design_docs/queries and POST /{db}/_local_docs/queries endpoints. Also, a new endpoint POST /{db}/_design/{ddoc}/_view/{view}/queries has been introduced to replace the ?queries parameter formerly provided for making multiple queries to a view. The old ?queries parameter is now deprecated and will be removed in a future release of CouchDB. The maximum http request limit, which had been lowered in 2.1.0, has been re-raised to a 4GB limit for now. (#1446). Ongoing discussion about the path forward for future releases is available in #1200 and #1253. #1118: The least recently used (LRU) cache of databases is now only updated on database write, not read. This has lead to significant performance enhancements on very busy clusters. To restore the previous behaviour, your local ini file can contain the block [couchdb] update_lru_on_read = true. #1153: The CouchDB replicator can now make use of the /_session endpoint rather than relying entirely on HTTP basic authentication headers. This can greatly improve replication performance. We encourage you to upgrade any nodes or clusters that regularly act as replication clients to use this new feature, which is enabled by default (#1462). #1283: The [couchdb] enable_database_recovery feature, which only soft-deletes databases in response to a DELETE /{db} call, is now documented in default.ini. #1330: CouchDB externals and OS daemons are now officially deprecated and no longer documented. Support for these features will be completely removed in a future release of CouchDB (probably 3.0.0). #1436: CouchDB proxy authentication now uses a proper chttpd_auth module, simplifying configuration in local ini files. While this is not a backward- compatible breaking change, it is best to update your local ini files to reference the new {chttpd_auth, proxy_authentication_handler} handler rather than the couch_httpd_auth version, as couch_httpd is in the process of being deprecated completely. #1476, #1477: The obsolete update_notification feature, which was replaced by /{db}/_changes feeds c. CouchDB 1.2, has been completely removed. This feature never worked in 2.0 for databases, only for shards, making it effectively useless.
2019-09-06 11:10:47 +02:00
couchdb/share/www/docs/_sources/setup/cluster.rst.txt
couchdb/share/www/docs/_sources/setup/index.rst.txt
couchdb/share/www/docs/_sources/setup/single-node.rst.txt
Update databases/couchdb to 2.1.1. couchdb 2.1.1 - CouchDB now supports compilation and running under Erlang/OTP 20.x - The couch_peruser functionality is now really fixed - The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customized via the ini file - It is now possible to modify shard maps for system databases - Due to an Erlang bug (ERL-343), invalid paths can be returned if volumes are mounted containing whitespace in their name (fixed) - The current node's local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.- The Dockerfile in the source repository has been retired - Fauxton now uses a version of React with a BSD license. - CouchDB now no longer decompresses documents just to determine their uncompressed size - The design document cache (ddoc_cache) has been rewritten to improve performance - Mango now supports partial indexes - Mango queries can now be paginated - Mango _find accepts an execution_stats parameter - Mango now requires that all of the fields in a candidate index must exist in a query's selector - Other minor improvements. couchdb 2.1.0 - The Mango _find endpoint supports a new combination operator, $allMatch. - New scheduling replicator. - Other minor improvements. See changelog for the 2.1.x branch for more: http://docs.couchdb.org/en/latest/whatsnew/2.1.html
2017-11-07 16:33:27 +01:00
couchdb/share/www/docs/_sources/whatsnew/0.10.rst.txt
couchdb/share/www/docs/_sources/whatsnew/0.11.rst.txt
couchdb/share/www/docs/_sources/whatsnew/0.8.rst.txt
couchdb/share/www/docs/_sources/whatsnew/0.9.rst.txt
couchdb/share/www/docs/_sources/whatsnew/1.0.rst.txt
couchdb/share/www/docs/_sources/whatsnew/1.1.rst.txt
couchdb/share/www/docs/_sources/whatsnew/1.2.rst.txt
couchdb/share/www/docs/_sources/whatsnew/1.3.rst.txt
couchdb/share/www/docs/_sources/whatsnew/1.4.rst.txt
couchdb/share/www/docs/_sources/whatsnew/1.5.rst.txt
couchdb/share/www/docs/_sources/whatsnew/1.6.rst.txt
couchdb: Upgrade to 2.3.1. Now works with current Erlang. Summary of changes between 2.1.x and 2.3.x are listed below. For a more readable version please see the following URLs: http://docs.couchdb.org/en/latest/whatsnew/2.3.html http://docs.couchdb.org/en/latest/whatsnew/2.2.html http://docs.couchdb.org/en/latest/whatsnew/2.1.html 2.3.x Branch Upgrade Notes #1602: To improve security, there have been major changes in the configuration of query servers, SSL support, and HTTP global handlers: Query servers are NO LONGER DEFINED in the .ini files, and can no longer be altered at run-time. The JavaScript and CoffeeScript query servers continue to be enabled by default. Setup differences have been moved from default.ini to the couchdb and couchdb.cmd start scripts respectively. Additional query servers can now be configured using environment variables: export COUCHDB_QUERY_SERVER_PYTHON="/path/to/python/query/server.py with args" couchdb where the last segment in the environment variable (_PYTHON) matches the usual lowercase(!) query language in the design doc language field (here, python.) Multiple query servers can be configured by using more environment variables. You can also override the default servers if you need to set command- line options (such as couchjs stack size): export COUCHDB_QUERY_SERVER_JAVASCRIPT="/path/to/couchjs /path/to/main.js -S <STACKSIZE>" couchdb The mango query server continues to be enabled by default. The Erlang query server continues to be disabled by default. This change adds a [native_query_servers] enable_erlang_query_server = BOOL setting (defaults to false) to enable the Erlang query server. If the legacy configuration for enabling the query server is detected, that is counted as a true setting as well, so existing configurations continue to work just fine. SSL Support Enabling SSL support in the ini file is now easier: [ssl] enable = true If the legacy httpsd configuration is found in your ini file, this will still enable SSL support, so existing configurations do not need to be changed. HTTP global handlers These are no longer defined in the default.ini file, but have been moved to the couch.app context. If you need to customize your handlers, you can modify the app context using a couchdb.config file as usual. #1602: Also to improve security, the deprecated os_daemons and couch_httpd_proxy functionality has been completely removed ahead of the planned CouchDB 3.0 release. We recommend the use of OS-level daemons such as runit, sysvinit, systemd, upstart, etc. to launch and maintain OS daemons instead, and the use of a reverse proxy server in front of CouchDB (such as haproxy) to proxy access to other services or domains alongside CouchDB. #1543: The node-local (default port 5986) /_restart endpoint has been replaced by the clustered (default port 5984) endpoint /_node/$node/_restart and /_node/_local/_restart endpoints. The node-local endpoint has been removed. #1764: All python scripts shipped with CouchDB, including couchup and the dev/run development cluster script, now specify and require Python 3.x. #1396: CouchDB is now compatible with Erlang 21.x. #1680: The embedded version of rebar used to build CouchDB has been updated to the last version of rebar2 available. This assists in building on non-x86 platforms. #1857: Refuse building with known bad versions of Erlang. 2.2.x Branch Upgrade Notes The minimum supported version of Erlang is now 17, not R16B03. Support for Erlang 21 is still ongoing and will be provided in a future release. The CouchDB replication client can now use the /_session endpoint when authenticating against remote CouchDB instances, improving performance since re-authorization does not have to be performed with every request. Because of this performance improvement, it is recommended to increase the PBKDF2 work factor beyond the default 10 to a modern default such as 10000. This is done via the local ini file setting [couch_httpd_auth] iterations = 10000. Do not do this if an older version of CouchDB is replicating TO this instance or cluster regularly, since CouchDB < 2.2.0 must perform authentication on every request and replication performance will suffer. A future version will make this increased number of iterations a default. #820, #1032: Multiple queries can now be made at the POST /{db}/_all_docs/queries, POST /{db}/_design_docs/queries and POST /{db}/_local_docs/queries endpoints. Also, a new endpoint POST /{db}/_design/{ddoc}/_view/{view}/queries has been introduced to replace the ?queries parameter formerly provided for making multiple queries to a view. The old ?queries parameter is now deprecated and will be removed in a future release of CouchDB. The maximum http request limit, which had been lowered in 2.1.0, has been re-raised to a 4GB limit for now. (#1446). Ongoing discussion about the path forward for future releases is available in #1200 and #1253. #1118: The least recently used (LRU) cache of databases is now only updated on database write, not read. This has lead to significant performance enhancements on very busy clusters. To restore the previous behaviour, your local ini file can contain the block [couchdb] update_lru_on_read = true. #1153: The CouchDB replicator can now make use of the /_session endpoint rather than relying entirely on HTTP basic authentication headers. This can greatly improve replication performance. We encourage you to upgrade any nodes or clusters that regularly act as replication clients to use this new feature, which is enabled by default (#1462). #1283: The [couchdb] enable_database_recovery feature, which only soft-deletes databases in response to a DELETE /{db} call, is now documented in default.ini. #1330: CouchDB externals and OS daemons are now officially deprecated and no longer documented. Support for these features will be completely removed in a future release of CouchDB (probably 3.0.0). #1436: CouchDB proxy authentication now uses a proper chttpd_auth module, simplifying configuration in local ini files. While this is not a backward- compatible breaking change, it is best to update your local ini files to reference the new {chttpd_auth, proxy_authentication_handler} handler rather than the couch_httpd_auth version, as couch_httpd is in the process of being deprecated completely. #1476, #1477: The obsolete update_notification feature, which was replaced by /{db}/_changes feeds c. CouchDB 1.2, has been completely removed. This feature never worked in 2.0 for databases, only for shards, making it effectively useless.
2019-09-06 11:10:47 +02:00
couchdb/share/www/docs/_sources/whatsnew/1.7.rst.txt
Update databases/couchdb to 2.1.1. couchdb 2.1.1 - CouchDB now supports compilation and running under Erlang/OTP 20.x - The couch_peruser functionality is now really fixed - The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customized via the ini file - It is now possible to modify shard maps for system databases - Due to an Erlang bug (ERL-343), invalid paths can be returned if volumes are mounted containing whitespace in their name (fixed) - The current node's local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.- The Dockerfile in the source repository has been retired - Fauxton now uses a version of React with a BSD license. - CouchDB now no longer decompresses documents just to determine their uncompressed size - The design document cache (ddoc_cache) has been rewritten to improve performance - Mango now supports partial indexes - Mango queries can now be paginated - Mango _find accepts an execution_stats parameter - Mango now requires that all of the fields in a candidate index must exist in a query's selector - Other minor improvements. couchdb 2.1.0 - The Mango _find endpoint supports a new combination operator, $allMatch. - New scheduling replicator. - Other minor improvements. See changelog for the 2.1.x branch for more: http://docs.couchdb.org/en/latest/whatsnew/2.1.html
2017-11-07 16:33:27 +01:00
couchdb/share/www/docs/_sources/whatsnew/2.0.rst.txt
couchdb/share/www/docs/_sources/whatsnew/2.1.rst.txt
couchdb: Upgrade to 2.3.1. Now works with current Erlang. Summary of changes between 2.1.x and 2.3.x are listed below. For a more readable version please see the following URLs: http://docs.couchdb.org/en/latest/whatsnew/2.3.html http://docs.couchdb.org/en/latest/whatsnew/2.2.html http://docs.couchdb.org/en/latest/whatsnew/2.1.html 2.3.x Branch Upgrade Notes #1602: To improve security, there have been major changes in the configuration of query servers, SSL support, and HTTP global handlers: Query servers are NO LONGER DEFINED in the .ini files, and can no longer be altered at run-time. The JavaScript and CoffeeScript query servers continue to be enabled by default. Setup differences have been moved from default.ini to the couchdb and couchdb.cmd start scripts respectively. Additional query servers can now be configured using environment variables: export COUCHDB_QUERY_SERVER_PYTHON="/path/to/python/query/server.py with args" couchdb where the last segment in the environment variable (_PYTHON) matches the usual lowercase(!) query language in the design doc language field (here, python.) Multiple query servers can be configured by using more environment variables. You can also override the default servers if you need to set command- line options (such as couchjs stack size): export COUCHDB_QUERY_SERVER_JAVASCRIPT="/path/to/couchjs /path/to/main.js -S <STACKSIZE>" couchdb The mango query server continues to be enabled by default. The Erlang query server continues to be disabled by default. This change adds a [native_query_servers] enable_erlang_query_server = BOOL setting (defaults to false) to enable the Erlang query server. If the legacy configuration for enabling the query server is detected, that is counted as a true setting as well, so existing configurations continue to work just fine. SSL Support Enabling SSL support in the ini file is now easier: [ssl] enable = true If the legacy httpsd configuration is found in your ini file, this will still enable SSL support, so existing configurations do not need to be changed. HTTP global handlers These are no longer defined in the default.ini file, but have been moved to the couch.app context. If you need to customize your handlers, you can modify the app context using a couchdb.config file as usual. #1602: Also to improve security, the deprecated os_daemons and couch_httpd_proxy functionality has been completely removed ahead of the planned CouchDB 3.0 release. We recommend the use of OS-level daemons such as runit, sysvinit, systemd, upstart, etc. to launch and maintain OS daemons instead, and the use of a reverse proxy server in front of CouchDB (such as haproxy) to proxy access to other services or domains alongside CouchDB. #1543: The node-local (default port 5986) /_restart endpoint has been replaced by the clustered (default port 5984) endpoint /_node/$node/_restart and /_node/_local/_restart endpoints. The node-local endpoint has been removed. #1764: All python scripts shipped with CouchDB, including couchup and the dev/run development cluster script, now specify and require Python 3.x. #1396: CouchDB is now compatible with Erlang 21.x. #1680: The embedded version of rebar used to build CouchDB has been updated to the last version of rebar2 available. This assists in building on non-x86 platforms. #1857: Refuse building with known bad versions of Erlang. 2.2.x Branch Upgrade Notes The minimum supported version of Erlang is now 17, not R16B03. Support for Erlang 21 is still ongoing and will be provided in a future release. The CouchDB replication client can now use the /_session endpoint when authenticating against remote CouchDB instances, improving performance since re-authorization does not have to be performed with every request. Because of this performance improvement, it is recommended to increase the PBKDF2 work factor beyond the default 10 to a modern default such as 10000. This is done via the local ini file setting [couch_httpd_auth] iterations = 10000. Do not do this if an older version of CouchDB is replicating TO this instance or cluster regularly, since CouchDB < 2.2.0 must perform authentication on every request and replication performance will suffer. A future version will make this increased number of iterations a default. #820, #1032: Multiple queries can now be made at the POST /{db}/_all_docs/queries, POST /{db}/_design_docs/queries and POST /{db}/_local_docs/queries endpoints. Also, a new endpoint POST /{db}/_design/{ddoc}/_view/{view}/queries has been introduced to replace the ?queries parameter formerly provided for making multiple queries to a view. The old ?queries parameter is now deprecated and will be removed in a future release of CouchDB. The maximum http request limit, which had been lowered in 2.1.0, has been re-raised to a 4GB limit for now. (#1446). Ongoing discussion about the path forward for future releases is available in #1200 and #1253. #1118: The least recently used (LRU) cache of databases is now only updated on database write, not read. This has lead to significant performance enhancements on very busy clusters. To restore the previous behaviour, your local ini file can contain the block [couchdb] update_lru_on_read = true. #1153: The CouchDB replicator can now make use of the /_session endpoint rather than relying entirely on HTTP basic authentication headers. This can greatly improve replication performance. We encourage you to upgrade any nodes or clusters that regularly act as replication clients to use this new feature, which is enabled by default (#1462). #1283: The [couchdb] enable_database_recovery feature, which only soft-deletes databases in response to a DELETE /{db} call, is now documented in default.ini. #1330: CouchDB externals and OS daemons are now officially deprecated and no longer documented. Support for these features will be completely removed in a future release of CouchDB (probably 3.0.0). #1436: CouchDB proxy authentication now uses a proper chttpd_auth module, simplifying configuration in local ini files. While this is not a backward- compatible breaking change, it is best to update your local ini files to reference the new {chttpd_auth, proxy_authentication_handler} handler rather than the couch_httpd_auth version, as couch_httpd is in the process of being deprecated completely. #1476, #1477: The obsolete update_notification feature, which was replaced by /{db}/_changes feeds c. CouchDB 1.2, has been completely removed. This feature never worked in 2.0 for databases, only for shards, making it effectively useless.
2019-09-06 11:10:47 +02:00
couchdb/share/www/docs/_sources/whatsnew/2.2.rst.txt
couchdb/share/www/docs/_sources/whatsnew/2.3.rst.txt
Update databases/couchdb to 2.1.1. couchdb 2.1.1 - CouchDB now supports compilation and running under Erlang/OTP 20.x - The couch_peruser functionality is now really fixed - The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customized via the ini file - It is now possible to modify shard maps for system databases - Due to an Erlang bug (ERL-343), invalid paths can be returned if volumes are mounted containing whitespace in their name (fixed) - The current node's local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.- The Dockerfile in the source repository has been retired - Fauxton now uses a version of React with a BSD license. - CouchDB now no longer decompresses documents just to determine their uncompressed size - The design document cache (ddoc_cache) has been rewritten to improve performance - Mango now supports partial indexes - Mango queries can now be paginated - Mango _find accepts an execution_stats parameter - Mango now requires that all of the fields in a candidate index must exist in a query's selector - Other minor improvements. couchdb 2.1.0 - The Mango _find endpoint supports a new combination operator, $allMatch. - New scheduling replicator. - Other minor improvements. See changelog for the 2.1.x branch for more: http://docs.couchdb.org/en/latest/whatsnew/2.1.html
2017-11-07 16:33:27 +01:00
couchdb/share/www/docs/_sources/whatsnew/index.rst.txt
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/share/www/docs/_static/ajax-loader.gif
couchdb/share/www/docs/_static/basic.css
couchdb/share/www/docs/_static/comment-bright.png
couchdb/share/www/docs/_static/comment-close.png
couchdb/share/www/docs/_static/comment.png
Update databases/couchdb to 2.1.1. couchdb 2.1.1 - CouchDB now supports compilation and running under Erlang/OTP 20.x - The couch_peruser functionality is now really fixed - The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customized via the ini file - It is now possible to modify shard maps for system databases - Due to an Erlang bug (ERL-343), invalid paths can be returned if volumes are mounted containing whitespace in their name (fixed) - The current node's local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.- The Dockerfile in the source repository has been retired - Fauxton now uses a version of React with a BSD license. - CouchDB now no longer decompresses documents just to determine their uncompressed size - The design document cache (ddoc_cache) has been rewritten to improve performance - Mango now supports partial indexes - Mango queries can now be paginated - Mango _find accepts an execution_stats parameter - Mango now requires that all of the fields in a candidate index must exist in a query's selector - Other minor improvements. couchdb 2.1.0 - The Mango _find endpoint supports a new combination operator, $allMatch. - New scheduling replicator. - Other minor improvements. See changelog for the 2.1.x branch for more: http://docs.couchdb.org/en/latest/whatsnew/2.1.html
2017-11-07 16:33:27 +01:00
couchdb/share/www/docs/_static/css/badge_only.css
couchdb/share/www/docs/_static/css/rtd_theme.css
couchdb/share/www/docs/_static/css/theme.css
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/share/www/docs/_static/doctools.js
couchdb/share/www/docs/_static/down-pressed.png
couchdb/share/www/docs/_static/down.png
couchdb/share/www/docs/_static/favicon.ico
couchdb/share/www/docs/_static/file.png
Update databases/couchdb to 2.1.1. couchdb 2.1.1 - CouchDB now supports compilation and running under Erlang/OTP 20.x - The couch_peruser functionality is now really fixed - The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customized via the ini file - It is now possible to modify shard maps for system databases - Due to an Erlang bug (ERL-343), invalid paths can be returned if volumes are mounted containing whitespace in their name (fixed) - The current node's local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.- The Dockerfile in the source repository has been retired - Fauxton now uses a version of React with a BSD license. - CouchDB now no longer decompresses documents just to determine their uncompressed size - The design document cache (ddoc_cache) has been rewritten to improve performance - Mango now supports partial indexes - Mango queries can now be paginated - Mango _find accepts an execution_stats parameter - Mango now requires that all of the fields in a candidate index must exist in a query's selector - Other minor improvements. couchdb 2.1.0 - The Mango _find endpoint supports a new combination operator, $allMatch. - New scheduling replicator. - Other minor improvements. See changelog for the 2.1.x branch for more: http://docs.couchdb.org/en/latest/whatsnew/2.1.html
2017-11-07 16:33:27 +01:00
couchdb/share/www/docs/_static/fonts/Inconsolata-Bold.ttf
couchdb/share/www/docs/_static/fonts/Inconsolata-Regular.ttf
couchdb/share/www/docs/_static/fonts/Lato-Bold.ttf
couchdb/share/www/docs/_static/fonts/Lato-Regular.ttf
couchdb/share/www/docs/_static/fonts/RobotoSlab-Bold.ttf
couchdb/share/www/docs/_static/fonts/RobotoSlab-Regular.ttf
couchdb/share/www/docs/_static/fonts/fontawesome-webfont.eot
couchdb/share/www/docs/_static/fonts/fontawesome-webfont.svg
couchdb/share/www/docs/_static/fonts/fontawesome-webfont.ttf
couchdb/share/www/docs/_static/fonts/fontawesome-webfont.woff
couchdb/share/www/docs/_static/jquery-3.1.0.js
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/share/www/docs/_static/jquery.js
Update databases/couchdb to 2.1.1. couchdb 2.1.1 - CouchDB now supports compilation and running under Erlang/OTP 20.x - The couch_peruser functionality is now really fixed - The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customized via the ini file - It is now possible to modify shard maps for system databases - Due to an Erlang bug (ERL-343), invalid paths can be returned if volumes are mounted containing whitespace in their name (fixed) - The current node's local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.- The Dockerfile in the source repository has been retired - Fauxton now uses a version of React with a BSD license. - CouchDB now no longer decompresses documents just to determine their uncompressed size - The design document cache (ddoc_cache) has been rewritten to improve performance - Mango now supports partial indexes - Mango queries can now be paginated - Mango _find accepts an execution_stats parameter - Mango now requires that all of the fields in a candidate index must exist in a query's selector - Other minor improvements. couchdb 2.1.0 - The Mango _find endpoint supports a new combination operator, $allMatch. - New scheduling replicator. - Other minor improvements. See changelog for the 2.1.x branch for more: http://docs.couchdb.org/en/latest/whatsnew/2.1.html
2017-11-07 16:33:27 +01:00
couchdb/share/www/docs/_static/js/modernizr.min.js
couchdb/share/www/docs/_static/js/theme.js
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/share/www/docs/_static/logo.png
couchdb/share/www/docs/_static/minus.png
couchdb/share/www/docs/_static/plus.png
couchdb/share/www/docs/_static/pygments.css
couchdb/share/www/docs/_static/searchtools.js
Update databases/couchdb to 2.1.1. couchdb 2.1.1 - CouchDB now supports compilation and running under Erlang/OTP 20.x - The couch_peruser functionality is now really fixed - The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customized via the ini file - It is now possible to modify shard maps for system databases - Due to an Erlang bug (ERL-343), invalid paths can be returned if volumes are mounted containing whitespace in their name (fixed) - The current node's local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.- The Dockerfile in the source repository has been retired - Fauxton now uses a version of React with a BSD license. - CouchDB now no longer decompresses documents just to determine their uncompressed size - The design document cache (ddoc_cache) has been rewritten to improve performance - Mango now supports partial indexes - Mango queries can now be paginated - Mango _find accepts an execution_stats parameter - Mango now requires that all of the fields in a candidate index must exist in a query's selector - Other minor improvements. couchdb 2.1.0 - The Mango _find endpoint supports a new combination operator, $allMatch. - New scheduling replicator. - Other minor improvements. See changelog for the 2.1.x branch for more: http://docs.couchdb.org/en/latest/whatsnew/2.1.html
2017-11-07 16:33:27 +01:00
couchdb/share/www/docs/_static/underscore-1.3.1.js
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/share/www/docs/_static/underscore.js
couchdb/share/www/docs/_static/up-pressed.png
couchdb/share/www/docs/_static/up.png
couchdb/share/www/docs/_static/websupport.js
couchdb/share/www/docs/about.html
couchdb/share/www/docs/api/basics.html
couchdb/share/www/docs/api/database/bulk-api.html
couchdb/share/www/docs/api/database/changes.html
couchdb/share/www/docs/api/database/common.html
couchdb/share/www/docs/api/database/compact.html
couchdb/share/www/docs/api/database/find.html
couchdb/share/www/docs/api/database/index.html
couchdb/share/www/docs/api/database/misc.html
couchdb/share/www/docs/api/database/security.html
couchdb: Upgrade to 2.3.1. Now works with current Erlang. Summary of changes between 2.1.x and 2.3.x are listed below. For a more readable version please see the following URLs: http://docs.couchdb.org/en/latest/whatsnew/2.3.html http://docs.couchdb.org/en/latest/whatsnew/2.2.html http://docs.couchdb.org/en/latest/whatsnew/2.1.html 2.3.x Branch Upgrade Notes #1602: To improve security, there have been major changes in the configuration of query servers, SSL support, and HTTP global handlers: Query servers are NO LONGER DEFINED in the .ini files, and can no longer be altered at run-time. The JavaScript and CoffeeScript query servers continue to be enabled by default. Setup differences have been moved from default.ini to the couchdb and couchdb.cmd start scripts respectively. Additional query servers can now be configured using environment variables: export COUCHDB_QUERY_SERVER_PYTHON="/path/to/python/query/server.py with args" couchdb where the last segment in the environment variable (_PYTHON) matches the usual lowercase(!) query language in the design doc language field (here, python.) Multiple query servers can be configured by using more environment variables. You can also override the default servers if you need to set command- line options (such as couchjs stack size): export COUCHDB_QUERY_SERVER_JAVASCRIPT="/path/to/couchjs /path/to/main.js -S <STACKSIZE>" couchdb The mango query server continues to be enabled by default. The Erlang query server continues to be disabled by default. This change adds a [native_query_servers] enable_erlang_query_server = BOOL setting (defaults to false) to enable the Erlang query server. If the legacy configuration for enabling the query server is detected, that is counted as a true setting as well, so existing configurations continue to work just fine. SSL Support Enabling SSL support in the ini file is now easier: [ssl] enable = true If the legacy httpsd configuration is found in your ini file, this will still enable SSL support, so existing configurations do not need to be changed. HTTP global handlers These are no longer defined in the default.ini file, but have been moved to the couch.app context. If you need to customize your handlers, you can modify the app context using a couchdb.config file as usual. #1602: Also to improve security, the deprecated os_daemons and couch_httpd_proxy functionality has been completely removed ahead of the planned CouchDB 3.0 release. We recommend the use of OS-level daemons such as runit, sysvinit, systemd, upstart, etc. to launch and maintain OS daemons instead, and the use of a reverse proxy server in front of CouchDB (such as haproxy) to proxy access to other services or domains alongside CouchDB. #1543: The node-local (default port 5986) /_restart endpoint has been replaced by the clustered (default port 5984) endpoint /_node/$node/_restart and /_node/_local/_restart endpoints. The node-local endpoint has been removed. #1764: All python scripts shipped with CouchDB, including couchup and the dev/run development cluster script, now specify and require Python 3.x. #1396: CouchDB is now compatible with Erlang 21.x. #1680: The embedded version of rebar used to build CouchDB has been updated to the last version of rebar2 available. This assists in building on non-x86 platforms. #1857: Refuse building with known bad versions of Erlang. 2.2.x Branch Upgrade Notes The minimum supported version of Erlang is now 17, not R16B03. Support for Erlang 21 is still ongoing and will be provided in a future release. The CouchDB replication client can now use the /_session endpoint when authenticating against remote CouchDB instances, improving performance since re-authorization does not have to be performed with every request. Because of this performance improvement, it is recommended to increase the PBKDF2 work factor beyond the default 10 to a modern default such as 10000. This is done via the local ini file setting [couch_httpd_auth] iterations = 10000. Do not do this if an older version of CouchDB is replicating TO this instance or cluster regularly, since CouchDB < 2.2.0 must perform authentication on every request and replication performance will suffer. A future version will make this increased number of iterations a default. #820, #1032: Multiple queries can now be made at the POST /{db}/_all_docs/queries, POST /{db}/_design_docs/queries and POST /{db}/_local_docs/queries endpoints. Also, a new endpoint POST /{db}/_design/{ddoc}/_view/{view}/queries has been introduced to replace the ?queries parameter formerly provided for making multiple queries to a view. The old ?queries parameter is now deprecated and will be removed in a future release of CouchDB. The maximum http request limit, which had been lowered in 2.1.0, has been re-raised to a 4GB limit for now. (#1446). Ongoing discussion about the path forward for future releases is available in #1200 and #1253. #1118: The least recently used (LRU) cache of databases is now only updated on database write, not read. This has lead to significant performance enhancements on very busy clusters. To restore the previous behaviour, your local ini file can contain the block [couchdb] update_lru_on_read = true. #1153: The CouchDB replicator can now make use of the /_session endpoint rather than relying entirely on HTTP basic authentication headers. This can greatly improve replication performance. We encourage you to upgrade any nodes or clusters that regularly act as replication clients to use this new feature, which is enabled by default (#1462). #1283: The [couchdb] enable_database_recovery feature, which only soft-deletes databases in response to a DELETE /{db} call, is now documented in default.ini. #1330: CouchDB externals and OS daemons are now officially deprecated and no longer documented. Support for these features will be completely removed in a future release of CouchDB (probably 3.0.0). #1436: CouchDB proxy authentication now uses a proper chttpd_auth module, simplifying configuration in local ini files. While this is not a backward- compatible breaking change, it is best to update your local ini files to reference the new {chttpd_auth, proxy_authentication_handler} handler rather than the couch_httpd_auth version, as couch_httpd is in the process of being deprecated completely. #1476, #1477: The obsolete update_notification feature, which was replaced by /{db}/_changes feeds c. CouchDB 1.2, has been completely removed. This feature never worked in 2.0 for databases, only for shards, making it effectively useless.
2019-09-06 11:10:47 +02:00
couchdb/share/www/docs/api/database/shard.html
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/share/www/docs/api/ddoc/common.html
couchdb/share/www/docs/api/ddoc/index.html
couchdb/share/www/docs/api/ddoc/render.html
couchdb/share/www/docs/api/ddoc/rewrites.html
couchdb/share/www/docs/api/ddoc/views.html
couchdb/share/www/docs/api/document/attachments.html
couchdb/share/www/docs/api/document/common.html
couchdb/share/www/docs/api/document/index.html
couchdb/share/www/docs/api/index.html
couchdb/share/www/docs/api/local.html
couchdb/share/www/docs/api/server/authn.html
couchdb/share/www/docs/api/server/common.html
couchdb/share/www/docs/api/server/configuration.html
couchdb/share/www/docs/api/server/index.html
couchdb: Upgrade to 2.3.1. Now works with current Erlang. Summary of changes between 2.1.x and 2.3.x are listed below. For a more readable version please see the following URLs: http://docs.couchdb.org/en/latest/whatsnew/2.3.html http://docs.couchdb.org/en/latest/whatsnew/2.2.html http://docs.couchdb.org/en/latest/whatsnew/2.1.html 2.3.x Branch Upgrade Notes #1602: To improve security, there have been major changes in the configuration of query servers, SSL support, and HTTP global handlers: Query servers are NO LONGER DEFINED in the .ini files, and can no longer be altered at run-time. The JavaScript and CoffeeScript query servers continue to be enabled by default. Setup differences have been moved from default.ini to the couchdb and couchdb.cmd start scripts respectively. Additional query servers can now be configured using environment variables: export COUCHDB_QUERY_SERVER_PYTHON="/path/to/python/query/server.py with args" couchdb where the last segment in the environment variable (_PYTHON) matches the usual lowercase(!) query language in the design doc language field (here, python.) Multiple query servers can be configured by using more environment variables. You can also override the default servers if you need to set command- line options (such as couchjs stack size): export COUCHDB_QUERY_SERVER_JAVASCRIPT="/path/to/couchjs /path/to/main.js -S <STACKSIZE>" couchdb The mango query server continues to be enabled by default. The Erlang query server continues to be disabled by default. This change adds a [native_query_servers] enable_erlang_query_server = BOOL setting (defaults to false) to enable the Erlang query server. If the legacy configuration for enabling the query server is detected, that is counted as a true setting as well, so existing configurations continue to work just fine. SSL Support Enabling SSL support in the ini file is now easier: [ssl] enable = true If the legacy httpsd configuration is found in your ini file, this will still enable SSL support, so existing configurations do not need to be changed. HTTP global handlers These are no longer defined in the default.ini file, but have been moved to the couch.app context. If you need to customize your handlers, you can modify the app context using a couchdb.config file as usual. #1602: Also to improve security, the deprecated os_daemons and couch_httpd_proxy functionality has been completely removed ahead of the planned CouchDB 3.0 release. We recommend the use of OS-level daemons such as runit, sysvinit, systemd, upstart, etc. to launch and maintain OS daemons instead, and the use of a reverse proxy server in front of CouchDB (such as haproxy) to proxy access to other services or domains alongside CouchDB. #1543: The node-local (default port 5986) /_restart endpoint has been replaced by the clustered (default port 5984) endpoint /_node/$node/_restart and /_node/_local/_restart endpoints. The node-local endpoint has been removed. #1764: All python scripts shipped with CouchDB, including couchup and the dev/run development cluster script, now specify and require Python 3.x. #1396: CouchDB is now compatible with Erlang 21.x. #1680: The embedded version of rebar used to build CouchDB has been updated to the last version of rebar2 available. This assists in building on non-x86 platforms. #1857: Refuse building with known bad versions of Erlang. 2.2.x Branch Upgrade Notes The minimum supported version of Erlang is now 17, not R16B03. Support for Erlang 21 is still ongoing and will be provided in a future release. The CouchDB replication client can now use the /_session endpoint when authenticating against remote CouchDB instances, improving performance since re-authorization does not have to be performed with every request. Because of this performance improvement, it is recommended to increase the PBKDF2 work factor beyond the default 10 to a modern default such as 10000. This is done via the local ini file setting [couch_httpd_auth] iterations = 10000. Do not do this if an older version of CouchDB is replicating TO this instance or cluster regularly, since CouchDB < 2.2.0 must perform authentication on every request and replication performance will suffer. A future version will make this increased number of iterations a default. #820, #1032: Multiple queries can now be made at the POST /{db}/_all_docs/queries, POST /{db}/_design_docs/queries and POST /{db}/_local_docs/queries endpoints. Also, a new endpoint POST /{db}/_design/{ddoc}/_view/{view}/queries has been introduced to replace the ?queries parameter formerly provided for making multiple queries to a view. The old ?queries parameter is now deprecated and will be removed in a future release of CouchDB. The maximum http request limit, which had been lowered in 2.1.0, has been re-raised to a 4GB limit for now. (#1446). Ongoing discussion about the path forward for future releases is available in #1200 and #1253. #1118: The least recently used (LRU) cache of databases is now only updated on database write, not read. This has lead to significant performance enhancements on very busy clusters. To restore the previous behaviour, your local ini file can contain the block [couchdb] update_lru_on_read = true. #1153: The CouchDB replicator can now make use of the /_session endpoint rather than relying entirely on HTTP basic authentication headers. This can greatly improve replication performance. We encourage you to upgrade any nodes or clusters that regularly act as replication clients to use this new feature, which is enabled by default (#1462). #1283: The [couchdb] enable_database_recovery feature, which only soft-deletes databases in response to a DELETE /{db} call, is now documented in default.ini. #1330: CouchDB externals and OS daemons are now officially deprecated and no longer documented. Support for these features will be completely removed in a future release of CouchDB (probably 3.0.0). #1436: CouchDB proxy authentication now uses a proper chttpd_auth module, simplifying configuration in local ini files. While this is not a backward- compatible breaking change, it is best to update your local ini files to reference the new {chttpd_auth, proxy_authentication_handler} handler rather than the couch_httpd_auth version, as couch_httpd is in the process of being deprecated completely. #1476, #1477: The obsolete update_notification feature, which was replaced by /{db}/_changes feeds c. CouchDB 1.2, has been completely removed. This feature never worked in 2.0 for databases, only for shards, making it effectively useless.
2019-09-06 11:10:47 +02:00
couchdb/share/www/docs/best-practices/documents.html
couchdb/share/www/docs/best-practices/forms.html
couchdb/share/www/docs/best-practices/index.html
couchdb/share/www/docs/best-practices/iso-date.html
couchdb/share/www/docs/best-practices/jsdevel.html
couchdb/share/www/docs/best-practices/reverse-proxies.html
couchdb/share/www/docs/best-practices/views.html
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/share/www/docs/cluster/databases.html
couchdb/share/www/docs/cluster/index.html
couchdb/share/www/docs/cluster/nodes.html
couchdb: Upgrade to 2.3.1. Now works with current Erlang. Summary of changes between 2.1.x and 2.3.x are listed below. For a more readable version please see the following URLs: http://docs.couchdb.org/en/latest/whatsnew/2.3.html http://docs.couchdb.org/en/latest/whatsnew/2.2.html http://docs.couchdb.org/en/latest/whatsnew/2.1.html 2.3.x Branch Upgrade Notes #1602: To improve security, there have been major changes in the configuration of query servers, SSL support, and HTTP global handlers: Query servers are NO LONGER DEFINED in the .ini files, and can no longer be altered at run-time. The JavaScript and CoffeeScript query servers continue to be enabled by default. Setup differences have been moved from default.ini to the couchdb and couchdb.cmd start scripts respectively. Additional query servers can now be configured using environment variables: export COUCHDB_QUERY_SERVER_PYTHON="/path/to/python/query/server.py with args" couchdb where the last segment in the environment variable (_PYTHON) matches the usual lowercase(!) query language in the design doc language field (here, python.) Multiple query servers can be configured by using more environment variables. You can also override the default servers if you need to set command- line options (such as couchjs stack size): export COUCHDB_QUERY_SERVER_JAVASCRIPT="/path/to/couchjs /path/to/main.js -S <STACKSIZE>" couchdb The mango query server continues to be enabled by default. The Erlang query server continues to be disabled by default. This change adds a [native_query_servers] enable_erlang_query_server = BOOL setting (defaults to false) to enable the Erlang query server. If the legacy configuration for enabling the query server is detected, that is counted as a true setting as well, so existing configurations continue to work just fine. SSL Support Enabling SSL support in the ini file is now easier: [ssl] enable = true If the legacy httpsd configuration is found in your ini file, this will still enable SSL support, so existing configurations do not need to be changed. HTTP global handlers These are no longer defined in the default.ini file, but have been moved to the couch.app context. If you need to customize your handlers, you can modify the app context using a couchdb.config file as usual. #1602: Also to improve security, the deprecated os_daemons and couch_httpd_proxy functionality has been completely removed ahead of the planned CouchDB 3.0 release. We recommend the use of OS-level daemons such as runit, sysvinit, systemd, upstart, etc. to launch and maintain OS daemons instead, and the use of a reverse proxy server in front of CouchDB (such as haproxy) to proxy access to other services or domains alongside CouchDB. #1543: The node-local (default port 5986) /_restart endpoint has been replaced by the clustered (default port 5984) endpoint /_node/$node/_restart and /_node/_local/_restart endpoints. The node-local endpoint has been removed. #1764: All python scripts shipped with CouchDB, including couchup and the dev/run development cluster script, now specify and require Python 3.x. #1396: CouchDB is now compatible with Erlang 21.x. #1680: The embedded version of rebar used to build CouchDB has been updated to the last version of rebar2 available. This assists in building on non-x86 platforms. #1857: Refuse building with known bad versions of Erlang. 2.2.x Branch Upgrade Notes The minimum supported version of Erlang is now 17, not R16B03. Support for Erlang 21 is still ongoing and will be provided in a future release. The CouchDB replication client can now use the /_session endpoint when authenticating against remote CouchDB instances, improving performance since re-authorization does not have to be performed with every request. Because of this performance improvement, it is recommended to increase the PBKDF2 work factor beyond the default 10 to a modern default such as 10000. This is done via the local ini file setting [couch_httpd_auth] iterations = 10000. Do not do this if an older version of CouchDB is replicating TO this instance or cluster regularly, since CouchDB < 2.2.0 must perform authentication on every request and replication performance will suffer. A future version will make this increased number of iterations a default. #820, #1032: Multiple queries can now be made at the POST /{db}/_all_docs/queries, POST /{db}/_design_docs/queries and POST /{db}/_local_docs/queries endpoints. Also, a new endpoint POST /{db}/_design/{ddoc}/_view/{view}/queries has been introduced to replace the ?queries parameter formerly provided for making multiple queries to a view. The old ?queries parameter is now deprecated and will be removed in a future release of CouchDB. The maximum http request limit, which had been lowered in 2.1.0, has been re-raised to a 4GB limit for now. (#1446). Ongoing discussion about the path forward for future releases is available in #1200 and #1253. #1118: The least recently used (LRU) cache of databases is now only updated on database write, not read. This has lead to significant performance enhancements on very busy clusters. To restore the previous behaviour, your local ini file can contain the block [couchdb] update_lru_on_read = true. #1153: The CouchDB replicator can now make use of the /_session endpoint rather than relying entirely on HTTP basic authentication headers. This can greatly improve replication performance. We encourage you to upgrade any nodes or clusters that regularly act as replication clients to use this new feature, which is enabled by default (#1462). #1283: The [couchdb] enable_database_recovery feature, which only soft-deletes databases in response to a DELETE /{db} call, is now documented in default.ini. #1330: CouchDB externals and OS daemons are now officially deprecated and no longer documented. Support for these features will be completely removed in a future release of CouchDB (probably 3.0.0). #1436: CouchDB proxy authentication now uses a proper chttpd_auth module, simplifying configuration in local ini files. While this is not a backward- compatible breaking change, it is best to update your local ini files to reference the new {chttpd_auth, proxy_authentication_handler} handler rather than the couch_httpd_auth version, as couch_httpd is in the process of being deprecated completely. #1476, #1477: The obsolete update_notification feature, which was replaced by /{db}/_changes feeds c. CouchDB 1.2, has been completely removed. This feature never worked in 2.0 for databases, only for shards, making it effectively useless.
2019-09-06 11:10:47 +02:00
couchdb/share/www/docs/cluster/purging.html
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/share/www/docs/cluster/sharding.html
couchdb/share/www/docs/cluster/theory.html
couchdb/share/www/docs/config-ref.html
couchdb/share/www/docs/config/auth.html
Update databases/couchdb to 2.1.1. couchdb 2.1.1 - CouchDB now supports compilation and running under Erlang/OTP 20.x - The couch_peruser functionality is now really fixed - The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customized via the ini file - It is now possible to modify shard maps for system databases - Due to an Erlang bug (ERL-343), invalid paths can be returned if volumes are mounted containing whitespace in their name (fixed) - The current node's local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.- The Dockerfile in the source repository has been retired - Fauxton now uses a version of React with a BSD license. - CouchDB now no longer decompresses documents just to determine their uncompressed size - The design document cache (ddoc_cache) has been rewritten to improve performance - Mango now supports partial indexes - Mango queries can now be paginated - Mango _find accepts an execution_stats parameter - Mango now requires that all of the fields in a candidate index must exist in a query's selector - Other minor improvements. couchdb 2.1.0 - The Mango _find endpoint supports a new combination operator, $allMatch. - New scheduling replicator. - Other minor improvements. See changelog for the 2.1.x branch for more: http://docs.couchdb.org/en/latest/whatsnew/2.1.html
2017-11-07 16:33:27 +01:00
couchdb/share/www/docs/config/cluster.html
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/share/www/docs/config/compaction.html
couchdb/share/www/docs/config/couch-peruser.html
couchdb/share/www/docs/config/couchdb.html
couchdb/share/www/docs/config/http.html
couchdb/share/www/docs/config/index.html
couchdb/share/www/docs/config/intro.html
couchdb/share/www/docs/config/logging.html
couchdb/share/www/docs/config/misc.html
couchdb/share/www/docs/config/query-servers.html
couchdb/share/www/docs/config/replicator.html
couchdb/share/www/docs/config/services.html
couchdb/share/www/docs/contributing.html
couchdb/share/www/docs/cve/2010-0009.html
couchdb/share/www/docs/cve/2010-2234.html
couchdb/share/www/docs/cve/2010-3854.html
couchdb/share/www/docs/cve/2012-5641.html
couchdb/share/www/docs/cve/2012-5649.html
couchdb/share/www/docs/cve/2012-5650.html
couchdb/share/www/docs/cve/2014-2668.html
couchdb: Upgrade to 2.3.1. Now works with current Erlang. Summary of changes between 2.1.x and 2.3.x are listed below. For a more readable version please see the following URLs: http://docs.couchdb.org/en/latest/whatsnew/2.3.html http://docs.couchdb.org/en/latest/whatsnew/2.2.html http://docs.couchdb.org/en/latest/whatsnew/2.1.html 2.3.x Branch Upgrade Notes #1602: To improve security, there have been major changes in the configuration of query servers, SSL support, and HTTP global handlers: Query servers are NO LONGER DEFINED in the .ini files, and can no longer be altered at run-time. The JavaScript and CoffeeScript query servers continue to be enabled by default. Setup differences have been moved from default.ini to the couchdb and couchdb.cmd start scripts respectively. Additional query servers can now be configured using environment variables: export COUCHDB_QUERY_SERVER_PYTHON="/path/to/python/query/server.py with args" couchdb where the last segment in the environment variable (_PYTHON) matches the usual lowercase(!) query language in the design doc language field (here, python.) Multiple query servers can be configured by using more environment variables. You can also override the default servers if you need to set command- line options (such as couchjs stack size): export COUCHDB_QUERY_SERVER_JAVASCRIPT="/path/to/couchjs /path/to/main.js -S <STACKSIZE>" couchdb The mango query server continues to be enabled by default. The Erlang query server continues to be disabled by default. This change adds a [native_query_servers] enable_erlang_query_server = BOOL setting (defaults to false) to enable the Erlang query server. If the legacy configuration for enabling the query server is detected, that is counted as a true setting as well, so existing configurations continue to work just fine. SSL Support Enabling SSL support in the ini file is now easier: [ssl] enable = true If the legacy httpsd configuration is found in your ini file, this will still enable SSL support, so existing configurations do not need to be changed. HTTP global handlers These are no longer defined in the default.ini file, but have been moved to the couch.app context. If you need to customize your handlers, you can modify the app context using a couchdb.config file as usual. #1602: Also to improve security, the deprecated os_daemons and couch_httpd_proxy functionality has been completely removed ahead of the planned CouchDB 3.0 release. We recommend the use of OS-level daemons such as runit, sysvinit, systemd, upstart, etc. to launch and maintain OS daemons instead, and the use of a reverse proxy server in front of CouchDB (such as haproxy) to proxy access to other services or domains alongside CouchDB. #1543: The node-local (default port 5986) /_restart endpoint has been replaced by the clustered (default port 5984) endpoint /_node/$node/_restart and /_node/_local/_restart endpoints. The node-local endpoint has been removed. #1764: All python scripts shipped with CouchDB, including couchup and the dev/run development cluster script, now specify and require Python 3.x. #1396: CouchDB is now compatible with Erlang 21.x. #1680: The embedded version of rebar used to build CouchDB has been updated to the last version of rebar2 available. This assists in building on non-x86 platforms. #1857: Refuse building with known bad versions of Erlang. 2.2.x Branch Upgrade Notes The minimum supported version of Erlang is now 17, not R16B03. Support for Erlang 21 is still ongoing and will be provided in a future release. The CouchDB replication client can now use the /_session endpoint when authenticating against remote CouchDB instances, improving performance since re-authorization does not have to be performed with every request. Because of this performance improvement, it is recommended to increase the PBKDF2 work factor beyond the default 10 to a modern default such as 10000. This is done via the local ini file setting [couch_httpd_auth] iterations = 10000. Do not do this if an older version of CouchDB is replicating TO this instance or cluster regularly, since CouchDB < 2.2.0 must perform authentication on every request and replication performance will suffer. A future version will make this increased number of iterations a default. #820, #1032: Multiple queries can now be made at the POST /{db}/_all_docs/queries, POST /{db}/_design_docs/queries and POST /{db}/_local_docs/queries endpoints. Also, a new endpoint POST /{db}/_design/{ddoc}/_view/{view}/queries has been introduced to replace the ?queries parameter formerly provided for making multiple queries to a view. The old ?queries parameter is now deprecated and will be removed in a future release of CouchDB. The maximum http request limit, which had been lowered in 2.1.0, has been re-raised to a 4GB limit for now. (#1446). Ongoing discussion about the path forward for future releases is available in #1200 and #1253. #1118: The least recently used (LRU) cache of databases is now only updated on database write, not read. This has lead to significant performance enhancements on very busy clusters. To restore the previous behaviour, your local ini file can contain the block [couchdb] update_lru_on_read = true. #1153: The CouchDB replicator can now make use of the /_session endpoint rather than relying entirely on HTTP basic authentication headers. This can greatly improve replication performance. We encourage you to upgrade any nodes or clusters that regularly act as replication clients to use this new feature, which is enabled by default (#1462). #1283: The [couchdb] enable_database_recovery feature, which only soft-deletes databases in response to a DELETE /{db} call, is now documented in default.ini. #1330: CouchDB externals and OS daemons are now officially deprecated and no longer documented. Support for these features will be completely removed in a future release of CouchDB (probably 3.0.0). #1436: CouchDB proxy authentication now uses a proper chttpd_auth module, simplifying configuration in local ini files. While this is not a backward- compatible breaking change, it is best to update your local ini files to reference the new {chttpd_auth, proxy_authentication_handler} handler rather than the couch_httpd_auth version, as couch_httpd is in the process of being deprecated completely. #1476, #1477: The obsolete update_notification feature, which was replaced by /{db}/_changes feeds c. CouchDB 1.2, has been completely removed. This feature never worked in 2.0 for databases, only for shards, making it effectively useless.
2019-09-06 11:10:47 +02:00
couchdb/share/www/docs/cve/2017-12635.html
couchdb/share/www/docs/cve/2017-12636.html
couchdb/share/www/docs/cve/2018-11769.html
couchdb/share/www/docs/cve/2018-17188.html
couchdb/share/www/docs/cve/2018-8007.html
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/share/www/docs/cve/index.html
Update databases/couchdb to 2.1.1. couchdb 2.1.1 - CouchDB now supports compilation and running under Erlang/OTP 20.x - The couch_peruser functionality is now really fixed - The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customized via the ini file - It is now possible to modify shard maps for system databases - Due to an Erlang bug (ERL-343), invalid paths can be returned if volumes are mounted containing whitespace in their name (fixed) - The current node's local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.- The Dockerfile in the source repository has been retired - Fauxton now uses a version of React with a BSD license. - CouchDB now no longer decompresses documents just to determine their uncompressed size - The design document cache (ddoc_cache) has been rewritten to improve performance - Mango now supports partial indexes - Mango queries can now be paginated - Mango _find accepts an execution_stats parameter - Mango now requires that all of the fields in a candidate index must exist in a query's selector - Other minor improvements. couchdb 2.1.0 - The Mango _find endpoint supports a new combination operator, $allMatch. - New scheduling replicator. - Other minor improvements. See changelog for the 2.1.x branch for more: http://docs.couchdb.org/en/latest/whatsnew/2.1.html
2017-11-07 16:33:27 +01:00
couchdb/share/www/docs/ddocs/ddocs.html
couchdb/share/www/docs/ddocs/index.html
couchdb/share/www/docs/ddocs/views/collation.html
couchdb/share/www/docs/ddocs/views/index.html
couchdb/share/www/docs/ddocs/views/intro.html
couchdb/share/www/docs/ddocs/views/joins.html
couchdb/share/www/docs/ddocs/views/nosql.html
couchdb/share/www/docs/ddocs/views/pagination.html
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/share/www/docs/download.html
couchdb/share/www/docs/experimental.html
couchdb/share/www/docs/fauxton/index.html
couchdb/share/www/docs/fauxton/install.html
couchdb/share/www/docs/http-api.html
couchdb/share/www/docs/index.html
Update databases/couchdb to 2.1.1. couchdb 2.1.1 - CouchDB now supports compilation and running under Erlang/OTP 20.x - The couch_peruser functionality is now really fixed - The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customized via the ini file - It is now possible to modify shard maps for system databases - Due to an Erlang bug (ERL-343), invalid paths can be returned if volumes are mounted containing whitespace in their name (fixed) - The current node's local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.- The Dockerfile in the source repository has been retired - Fauxton now uses a version of React with a BSD license. - CouchDB now no longer decompresses documents just to determine their uncompressed size - The design document cache (ddoc_cache) has been rewritten to improve performance - Mango now supports partial indexes - Mango queries can now be paginated - Mango _find accepts an execution_stats parameter - Mango now requires that all of the fields in a candidate index must exist in a query's selector - Other minor improvements. couchdb 2.1.0 - The Mango _find endpoint supports a new combination operator, $allMatch. - New scheduling replicator. - Other minor improvements. See changelog for the 2.1.x branch for more: http://docs.couchdb.org/en/latest/whatsnew/2.1.html
2017-11-07 16:33:27 +01:00
couchdb/share/www/docs/install/docker.html
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/share/www/docs/install/freebsd.html
couchdb/share/www/docs/install/index.html
couchdb/share/www/docs/install/mac.html
Update databases/couchdb to 2.1.1. couchdb 2.1.1 - CouchDB now supports compilation and running under Erlang/OTP 20.x - The couch_peruser functionality is now really fixed - The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customized via the ini file - It is now possible to modify shard maps for system databases - Due to an Erlang bug (ERL-343), invalid paths can be returned if volumes are mounted containing whitespace in their name (fixed) - The current node's local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.- The Dockerfile in the source repository has been retired - Fauxton now uses a version of React with a BSD license. - CouchDB now no longer decompresses documents just to determine their uncompressed size - The design document cache (ddoc_cache) has been rewritten to improve performance - Mango now supports partial indexes - Mango queries can now be paginated - Mango _find accepts an execution_stats parameter - Mango now requires that all of the fields in a candidate index must exist in a query's selector - Other minor improvements. couchdb 2.1.0 - The Mango _find endpoint supports a new combination operator, $allMatch. - New scheduling replicator. - Other minor improvements. See changelog for the 2.1.x branch for more: http://docs.couchdb.org/en/latest/whatsnew/2.1.html
2017-11-07 16:33:27 +01:00
couchdb/share/www/docs/install/snap.html
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/share/www/docs/install/troubleshooting.html
couchdb/share/www/docs/install/unix.html
Update databases/couchdb to 2.1.1. couchdb 2.1.1 - CouchDB now supports compilation and running under Erlang/OTP 20.x - The couch_peruser functionality is now really fixed - The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customized via the ini file - It is now possible to modify shard maps for system databases - Due to an Erlang bug (ERL-343), invalid paths can be returned if volumes are mounted containing whitespace in their name (fixed) - The current node's local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.- The Dockerfile in the source repository has been retired - Fauxton now uses a version of React with a BSD license. - CouchDB now no longer decompresses documents just to determine their uncompressed size - The design document cache (ddoc_cache) has been rewritten to improve performance - Mango now supports partial indexes - Mango queries can now be paginated - Mango _find accepts an execution_stats parameter - Mango now requires that all of the fields in a candidate index must exist in a query's selector - Other minor improvements. couchdb 2.1.0 - The Mango _find endpoint supports a new combination operator, $allMatch. - New scheduling replicator. - Other minor improvements. See changelog for the 2.1.x branch for more: http://docs.couchdb.org/en/latest/whatsnew/2.1.html
2017-11-07 16:33:27 +01:00
couchdb/share/www/docs/install/upgrading.html
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/share/www/docs/install/windows.html
couchdb/share/www/docs/intro/api.html
couchdb/share/www/docs/intro/consistency.html
couchdb/share/www/docs/intro/curl.html
couchdb/share/www/docs/intro/index.html
couchdb/share/www/docs/intro/overview.html
couchdb/share/www/docs/intro/security.html
couchdb/share/www/docs/intro/tour.html
couchdb/share/www/docs/intro/why.html
couchdb/share/www/docs/json-structure.html
couchdb: Upgrade to 2.3.1. Now works with current Erlang. Summary of changes between 2.1.x and 2.3.x are listed below. For a more readable version please see the following URLs: http://docs.couchdb.org/en/latest/whatsnew/2.3.html http://docs.couchdb.org/en/latest/whatsnew/2.2.html http://docs.couchdb.org/en/latest/whatsnew/2.1.html 2.3.x Branch Upgrade Notes #1602: To improve security, there have been major changes in the configuration of query servers, SSL support, and HTTP global handlers: Query servers are NO LONGER DEFINED in the .ini files, and can no longer be altered at run-time. The JavaScript and CoffeeScript query servers continue to be enabled by default. Setup differences have been moved from default.ini to the couchdb and couchdb.cmd start scripts respectively. Additional query servers can now be configured using environment variables: export COUCHDB_QUERY_SERVER_PYTHON="/path/to/python/query/server.py with args" couchdb where the last segment in the environment variable (_PYTHON) matches the usual lowercase(!) query language in the design doc language field (here, python.) Multiple query servers can be configured by using more environment variables. You can also override the default servers if you need to set command- line options (such as couchjs stack size): export COUCHDB_QUERY_SERVER_JAVASCRIPT="/path/to/couchjs /path/to/main.js -S <STACKSIZE>" couchdb The mango query server continues to be enabled by default. The Erlang query server continues to be disabled by default. This change adds a [native_query_servers] enable_erlang_query_server = BOOL setting (defaults to false) to enable the Erlang query server. If the legacy configuration for enabling the query server is detected, that is counted as a true setting as well, so existing configurations continue to work just fine. SSL Support Enabling SSL support in the ini file is now easier: [ssl] enable = true If the legacy httpsd configuration is found in your ini file, this will still enable SSL support, so existing configurations do not need to be changed. HTTP global handlers These are no longer defined in the default.ini file, but have been moved to the couch.app context. If you need to customize your handlers, you can modify the app context using a couchdb.config file as usual. #1602: Also to improve security, the deprecated os_daemons and couch_httpd_proxy functionality has been completely removed ahead of the planned CouchDB 3.0 release. We recommend the use of OS-level daemons such as runit, sysvinit, systemd, upstart, etc. to launch and maintain OS daemons instead, and the use of a reverse proxy server in front of CouchDB (such as haproxy) to proxy access to other services or domains alongside CouchDB. #1543: The node-local (default port 5986) /_restart endpoint has been replaced by the clustered (default port 5984) endpoint /_node/$node/_restart and /_node/_local/_restart endpoints. The node-local endpoint has been removed. #1764: All python scripts shipped with CouchDB, including couchup and the dev/run development cluster script, now specify and require Python 3.x. #1396: CouchDB is now compatible with Erlang 21.x. #1680: The embedded version of rebar used to build CouchDB has been updated to the last version of rebar2 available. This assists in building on non-x86 platforms. #1857: Refuse building with known bad versions of Erlang. 2.2.x Branch Upgrade Notes The minimum supported version of Erlang is now 17, not R16B03. Support for Erlang 21 is still ongoing and will be provided in a future release. The CouchDB replication client can now use the /_session endpoint when authenticating against remote CouchDB instances, improving performance since re-authorization does not have to be performed with every request. Because of this performance improvement, it is recommended to increase the PBKDF2 work factor beyond the default 10 to a modern default such as 10000. This is done via the local ini file setting [couch_httpd_auth] iterations = 10000. Do not do this if an older version of CouchDB is replicating TO this instance or cluster regularly, since CouchDB < 2.2.0 must perform authentication on every request and replication performance will suffer. A future version will make this increased number of iterations a default. #820, #1032: Multiple queries can now be made at the POST /{db}/_all_docs/queries, POST /{db}/_design_docs/queries and POST /{db}/_local_docs/queries endpoints. Also, a new endpoint POST /{db}/_design/{ddoc}/_view/{view}/queries has been introduced to replace the ?queries parameter formerly provided for making multiple queries to a view. The old ?queries parameter is now deprecated and will be removed in a future release of CouchDB. The maximum http request limit, which had been lowered in 2.1.0, has been re-raised to a 4GB limit for now. (#1446). Ongoing discussion about the path forward for future releases is available in #1200 and #1253. #1118: The least recently used (LRU) cache of databases is now only updated on database write, not read. This has lead to significant performance enhancements on very busy clusters. To restore the previous behaviour, your local ini file can contain the block [couchdb] update_lru_on_read = true. #1153: The CouchDB replicator can now make use of the /_session endpoint rather than relying entirely on HTTP basic authentication headers. This can greatly improve replication performance. We encourage you to upgrade any nodes or clusters that regularly act as replication clients to use this new feature, which is enabled by default (#1462). #1283: The [couchdb] enable_database_recovery feature, which only soft-deletes databases in response to a DELETE /{db} call, is now documented in default.ini. #1330: CouchDB externals and OS daemons are now officially deprecated and no longer documented. Support for these features will be completely removed in a future release of CouchDB (probably 3.0.0). #1436: CouchDB proxy authentication now uses a proper chttpd_auth module, simplifying configuration in local ini files. While this is not a backward- compatible breaking change, it is best to update your local ini files to reference the new {chttpd_auth, proxy_authentication_handler} handler rather than the couch_httpd_auth version, as couch_httpd is in the process of being deprecated completely. #1476, #1477: The obsolete update_notification feature, which was replaced by /{db}/_changes feeds c. CouchDB 1.2, has been completely removed. This feature never worked in 2.0 for databases, only for shards, making it effectively useless.
2019-09-06 11:10:47 +02:00
couchdb/share/www/docs/maintenance/backups.html
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/share/www/docs/maintenance/compaction.html
couchdb/share/www/docs/maintenance/index.html
couchdb/share/www/docs/maintenance/performance.html
couchdb/share/www/docs/objects.inv
couchdb/share/www/docs/query-server/erlang.html
couchdb/share/www/docs/query-server/index.html
couchdb/share/www/docs/query-server/javascript.html
couchdb/share/www/docs/query-server/protocol.html
couchdb/share/www/docs/replication/conflicts.html
couchdb/share/www/docs/replication/index.html
couchdb/share/www/docs/replication/intro.html
couchdb/share/www/docs/replication/protocol.html
couchdb/share/www/docs/replication/replicator.html
couchdb/share/www/docs/search.html
couchdb/share/www/docs/searchindex.js
couchdb: Upgrade to 2.3.1. Now works with current Erlang. Summary of changes between 2.1.x and 2.3.x are listed below. For a more readable version please see the following URLs: http://docs.couchdb.org/en/latest/whatsnew/2.3.html http://docs.couchdb.org/en/latest/whatsnew/2.2.html http://docs.couchdb.org/en/latest/whatsnew/2.1.html 2.3.x Branch Upgrade Notes #1602: To improve security, there have been major changes in the configuration of query servers, SSL support, and HTTP global handlers: Query servers are NO LONGER DEFINED in the .ini files, and can no longer be altered at run-time. The JavaScript and CoffeeScript query servers continue to be enabled by default. Setup differences have been moved from default.ini to the couchdb and couchdb.cmd start scripts respectively. Additional query servers can now be configured using environment variables: export COUCHDB_QUERY_SERVER_PYTHON="/path/to/python/query/server.py with args" couchdb where the last segment in the environment variable (_PYTHON) matches the usual lowercase(!) query language in the design doc language field (here, python.) Multiple query servers can be configured by using more environment variables. You can also override the default servers if you need to set command- line options (such as couchjs stack size): export COUCHDB_QUERY_SERVER_JAVASCRIPT="/path/to/couchjs /path/to/main.js -S <STACKSIZE>" couchdb The mango query server continues to be enabled by default. The Erlang query server continues to be disabled by default. This change adds a [native_query_servers] enable_erlang_query_server = BOOL setting (defaults to false) to enable the Erlang query server. If the legacy configuration for enabling the query server is detected, that is counted as a true setting as well, so existing configurations continue to work just fine. SSL Support Enabling SSL support in the ini file is now easier: [ssl] enable = true If the legacy httpsd configuration is found in your ini file, this will still enable SSL support, so existing configurations do not need to be changed. HTTP global handlers These are no longer defined in the default.ini file, but have been moved to the couch.app context. If you need to customize your handlers, you can modify the app context using a couchdb.config file as usual. #1602: Also to improve security, the deprecated os_daemons and couch_httpd_proxy functionality has been completely removed ahead of the planned CouchDB 3.0 release. We recommend the use of OS-level daemons such as runit, sysvinit, systemd, upstart, etc. to launch and maintain OS daemons instead, and the use of a reverse proxy server in front of CouchDB (such as haproxy) to proxy access to other services or domains alongside CouchDB. #1543: The node-local (default port 5986) /_restart endpoint has been replaced by the clustered (default port 5984) endpoint /_node/$node/_restart and /_node/_local/_restart endpoints. The node-local endpoint has been removed. #1764: All python scripts shipped with CouchDB, including couchup and the dev/run development cluster script, now specify and require Python 3.x. #1396: CouchDB is now compatible with Erlang 21.x. #1680: The embedded version of rebar used to build CouchDB has been updated to the last version of rebar2 available. This assists in building on non-x86 platforms. #1857: Refuse building with known bad versions of Erlang. 2.2.x Branch Upgrade Notes The minimum supported version of Erlang is now 17, not R16B03. Support for Erlang 21 is still ongoing and will be provided in a future release. The CouchDB replication client can now use the /_session endpoint when authenticating against remote CouchDB instances, improving performance since re-authorization does not have to be performed with every request. Because of this performance improvement, it is recommended to increase the PBKDF2 work factor beyond the default 10 to a modern default such as 10000. This is done via the local ini file setting [couch_httpd_auth] iterations = 10000. Do not do this if an older version of CouchDB is replicating TO this instance or cluster regularly, since CouchDB < 2.2.0 must perform authentication on every request and replication performance will suffer. A future version will make this increased number of iterations a default. #820, #1032: Multiple queries can now be made at the POST /{db}/_all_docs/queries, POST /{db}/_design_docs/queries and POST /{db}/_local_docs/queries endpoints. Also, a new endpoint POST /{db}/_design/{ddoc}/_view/{view}/queries has been introduced to replace the ?queries parameter formerly provided for making multiple queries to a view. The old ?queries parameter is now deprecated and will be removed in a future release of CouchDB. The maximum http request limit, which had been lowered in 2.1.0, has been re-raised to a 4GB limit for now. (#1446). Ongoing discussion about the path forward for future releases is available in #1200 and #1253. #1118: The least recently used (LRU) cache of databases is now only updated on database write, not read. This has lead to significant performance enhancements on very busy clusters. To restore the previous behaviour, your local ini file can contain the block [couchdb] update_lru_on_read = true. #1153: The CouchDB replicator can now make use of the /_session endpoint rather than relying entirely on HTTP basic authentication headers. This can greatly improve replication performance. We encourage you to upgrade any nodes or clusters that regularly act as replication clients to use this new feature, which is enabled by default (#1462). #1283: The [couchdb] enable_database_recovery feature, which only soft-deletes databases in response to a DELETE /{db} call, is now documented in default.ini. #1330: CouchDB externals and OS daemons are now officially deprecated and no longer documented. Support for these features will be completely removed in a future release of CouchDB (probably 3.0.0). #1436: CouchDB proxy authentication now uses a proper chttpd_auth module, simplifying configuration in local ini files. While this is not a backward- compatible breaking change, it is best to update your local ini files to reference the new {chttpd_auth, proxy_authentication_handler} handler rather than the couch_httpd_auth version, as couch_httpd is in the process of being deprecated completely. #1476, #1477: The obsolete update_notification feature, which was replaced by /{db}/_changes feeds c. CouchDB 1.2, has been completely removed. This feature never worked in 2.0 for databases, only for shards, making it effectively useless.
2019-09-06 11:10:47 +02:00
couchdb/share/www/docs/setup/cluster.html
couchdb/share/www/docs/setup/index.html
couchdb/share/www/docs/setup/single-node.html
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/share/www/docs/whatsnew/0.10.html
couchdb/share/www/docs/whatsnew/0.11.html
couchdb/share/www/docs/whatsnew/0.8.html
couchdb/share/www/docs/whatsnew/0.9.html
couchdb/share/www/docs/whatsnew/1.0.html
couchdb/share/www/docs/whatsnew/1.1.html
couchdb/share/www/docs/whatsnew/1.2.html
couchdb/share/www/docs/whatsnew/1.3.html
couchdb/share/www/docs/whatsnew/1.4.html
couchdb/share/www/docs/whatsnew/1.5.html
couchdb/share/www/docs/whatsnew/1.6.html
couchdb: Upgrade to 2.3.1. Now works with current Erlang. Summary of changes between 2.1.x and 2.3.x are listed below. For a more readable version please see the following URLs: http://docs.couchdb.org/en/latest/whatsnew/2.3.html http://docs.couchdb.org/en/latest/whatsnew/2.2.html http://docs.couchdb.org/en/latest/whatsnew/2.1.html 2.3.x Branch Upgrade Notes #1602: To improve security, there have been major changes in the configuration of query servers, SSL support, and HTTP global handlers: Query servers are NO LONGER DEFINED in the .ini files, and can no longer be altered at run-time. The JavaScript and CoffeeScript query servers continue to be enabled by default. Setup differences have been moved from default.ini to the couchdb and couchdb.cmd start scripts respectively. Additional query servers can now be configured using environment variables: export COUCHDB_QUERY_SERVER_PYTHON="/path/to/python/query/server.py with args" couchdb where the last segment in the environment variable (_PYTHON) matches the usual lowercase(!) query language in the design doc language field (here, python.) Multiple query servers can be configured by using more environment variables. You can also override the default servers if you need to set command- line options (such as couchjs stack size): export COUCHDB_QUERY_SERVER_JAVASCRIPT="/path/to/couchjs /path/to/main.js -S <STACKSIZE>" couchdb The mango query server continues to be enabled by default. The Erlang query server continues to be disabled by default. This change adds a [native_query_servers] enable_erlang_query_server = BOOL setting (defaults to false) to enable the Erlang query server. If the legacy configuration for enabling the query server is detected, that is counted as a true setting as well, so existing configurations continue to work just fine. SSL Support Enabling SSL support in the ini file is now easier: [ssl] enable = true If the legacy httpsd configuration is found in your ini file, this will still enable SSL support, so existing configurations do not need to be changed. HTTP global handlers These are no longer defined in the default.ini file, but have been moved to the couch.app context. If you need to customize your handlers, you can modify the app context using a couchdb.config file as usual. #1602: Also to improve security, the deprecated os_daemons and couch_httpd_proxy functionality has been completely removed ahead of the planned CouchDB 3.0 release. We recommend the use of OS-level daemons such as runit, sysvinit, systemd, upstart, etc. to launch and maintain OS daemons instead, and the use of a reverse proxy server in front of CouchDB (such as haproxy) to proxy access to other services or domains alongside CouchDB. #1543: The node-local (default port 5986) /_restart endpoint has been replaced by the clustered (default port 5984) endpoint /_node/$node/_restart and /_node/_local/_restart endpoints. The node-local endpoint has been removed. #1764: All python scripts shipped with CouchDB, including couchup and the dev/run development cluster script, now specify and require Python 3.x. #1396: CouchDB is now compatible with Erlang 21.x. #1680: The embedded version of rebar used to build CouchDB has been updated to the last version of rebar2 available. This assists in building on non-x86 platforms. #1857: Refuse building with known bad versions of Erlang. 2.2.x Branch Upgrade Notes The minimum supported version of Erlang is now 17, not R16B03. Support for Erlang 21 is still ongoing and will be provided in a future release. The CouchDB replication client can now use the /_session endpoint when authenticating against remote CouchDB instances, improving performance since re-authorization does not have to be performed with every request. Because of this performance improvement, it is recommended to increase the PBKDF2 work factor beyond the default 10 to a modern default such as 10000. This is done via the local ini file setting [couch_httpd_auth] iterations = 10000. Do not do this if an older version of CouchDB is replicating TO this instance or cluster regularly, since CouchDB < 2.2.0 must perform authentication on every request and replication performance will suffer. A future version will make this increased number of iterations a default. #820, #1032: Multiple queries can now be made at the POST /{db}/_all_docs/queries, POST /{db}/_design_docs/queries and POST /{db}/_local_docs/queries endpoints. Also, a new endpoint POST /{db}/_design/{ddoc}/_view/{view}/queries has been introduced to replace the ?queries parameter formerly provided for making multiple queries to a view. The old ?queries parameter is now deprecated and will be removed in a future release of CouchDB. The maximum http request limit, which had been lowered in 2.1.0, has been re-raised to a 4GB limit for now. (#1446). Ongoing discussion about the path forward for future releases is available in #1200 and #1253. #1118: The least recently used (LRU) cache of databases is now only updated on database write, not read. This has lead to significant performance enhancements on very busy clusters. To restore the previous behaviour, your local ini file can contain the block [couchdb] update_lru_on_read = true. #1153: The CouchDB replicator can now make use of the /_session endpoint rather than relying entirely on HTTP basic authentication headers. This can greatly improve replication performance. We encourage you to upgrade any nodes or clusters that regularly act as replication clients to use this new feature, which is enabled by default (#1462). #1283: The [couchdb] enable_database_recovery feature, which only soft-deletes databases in response to a DELETE /{db} call, is now documented in default.ini. #1330: CouchDB externals and OS daemons are now officially deprecated and no longer documented. Support for these features will be completely removed in a future release of CouchDB (probably 3.0.0). #1436: CouchDB proxy authentication now uses a proper chttpd_auth module, simplifying configuration in local ini files. While this is not a backward- compatible breaking change, it is best to update your local ini files to reference the new {chttpd_auth, proxy_authentication_handler} handler rather than the couch_httpd_auth version, as couch_httpd is in the process of being deprecated completely. #1476, #1477: The obsolete update_notification feature, which was replaced by /{db}/_changes feeds c. CouchDB 1.2, has been completely removed. This feature never worked in 2.0 for databases, only for shards, making it effectively useless.
2019-09-06 11:10:47 +02:00
couchdb/share/www/docs/whatsnew/1.7.html
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/share/www/docs/whatsnew/2.0.html
Update databases/couchdb to 2.1.1. couchdb 2.1.1 - CouchDB now supports compilation and running under Erlang/OTP 20.x - The couch_peruser functionality is now really fixed - The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customized via the ini file - It is now possible to modify shard maps for system databases - Due to an Erlang bug (ERL-343), invalid paths can be returned if volumes are mounted containing whitespace in their name (fixed) - The current node's local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.- The Dockerfile in the source repository has been retired - Fauxton now uses a version of React with a BSD license. - CouchDB now no longer decompresses documents just to determine their uncompressed size - The design document cache (ddoc_cache) has been rewritten to improve performance - Mango now supports partial indexes - Mango queries can now be paginated - Mango _find accepts an execution_stats parameter - Mango now requires that all of the fields in a candidate index must exist in a query's selector - Other minor improvements. couchdb 2.1.0 - The Mango _find endpoint supports a new combination operator, $allMatch. - New scheduling replicator. - Other minor improvements. See changelog for the 2.1.x branch for more: http://docs.couchdb.org/en/latest/whatsnew/2.1.html
2017-11-07 16:33:27 +01:00
couchdb/share/www/docs/whatsnew/2.1.html
couchdb: Upgrade to 2.3.1. Now works with current Erlang. Summary of changes between 2.1.x and 2.3.x are listed below. For a more readable version please see the following URLs: http://docs.couchdb.org/en/latest/whatsnew/2.3.html http://docs.couchdb.org/en/latest/whatsnew/2.2.html http://docs.couchdb.org/en/latest/whatsnew/2.1.html 2.3.x Branch Upgrade Notes #1602: To improve security, there have been major changes in the configuration of query servers, SSL support, and HTTP global handlers: Query servers are NO LONGER DEFINED in the .ini files, and can no longer be altered at run-time. The JavaScript and CoffeeScript query servers continue to be enabled by default. Setup differences have been moved from default.ini to the couchdb and couchdb.cmd start scripts respectively. Additional query servers can now be configured using environment variables: export COUCHDB_QUERY_SERVER_PYTHON="/path/to/python/query/server.py with args" couchdb where the last segment in the environment variable (_PYTHON) matches the usual lowercase(!) query language in the design doc language field (here, python.) Multiple query servers can be configured by using more environment variables. You can also override the default servers if you need to set command- line options (such as couchjs stack size): export COUCHDB_QUERY_SERVER_JAVASCRIPT="/path/to/couchjs /path/to/main.js -S <STACKSIZE>" couchdb The mango query server continues to be enabled by default. The Erlang query server continues to be disabled by default. This change adds a [native_query_servers] enable_erlang_query_server = BOOL setting (defaults to false) to enable the Erlang query server. If the legacy configuration for enabling the query server is detected, that is counted as a true setting as well, so existing configurations continue to work just fine. SSL Support Enabling SSL support in the ini file is now easier: [ssl] enable = true If the legacy httpsd configuration is found in your ini file, this will still enable SSL support, so existing configurations do not need to be changed. HTTP global handlers These are no longer defined in the default.ini file, but have been moved to the couch.app context. If you need to customize your handlers, you can modify the app context using a couchdb.config file as usual. #1602: Also to improve security, the deprecated os_daemons and couch_httpd_proxy functionality has been completely removed ahead of the planned CouchDB 3.0 release. We recommend the use of OS-level daemons such as runit, sysvinit, systemd, upstart, etc. to launch and maintain OS daemons instead, and the use of a reverse proxy server in front of CouchDB (such as haproxy) to proxy access to other services or domains alongside CouchDB. #1543: The node-local (default port 5986) /_restart endpoint has been replaced by the clustered (default port 5984) endpoint /_node/$node/_restart and /_node/_local/_restart endpoints. The node-local endpoint has been removed. #1764: All python scripts shipped with CouchDB, including couchup and the dev/run development cluster script, now specify and require Python 3.x. #1396: CouchDB is now compatible with Erlang 21.x. #1680: The embedded version of rebar used to build CouchDB has been updated to the last version of rebar2 available. This assists in building on non-x86 platforms. #1857: Refuse building with known bad versions of Erlang. 2.2.x Branch Upgrade Notes The minimum supported version of Erlang is now 17, not R16B03. Support for Erlang 21 is still ongoing and will be provided in a future release. The CouchDB replication client can now use the /_session endpoint when authenticating against remote CouchDB instances, improving performance since re-authorization does not have to be performed with every request. Because of this performance improvement, it is recommended to increase the PBKDF2 work factor beyond the default 10 to a modern default such as 10000. This is done via the local ini file setting [couch_httpd_auth] iterations = 10000. Do not do this if an older version of CouchDB is replicating TO this instance or cluster regularly, since CouchDB < 2.2.0 must perform authentication on every request and replication performance will suffer. A future version will make this increased number of iterations a default. #820, #1032: Multiple queries can now be made at the POST /{db}/_all_docs/queries, POST /{db}/_design_docs/queries and POST /{db}/_local_docs/queries endpoints. Also, a new endpoint POST /{db}/_design/{ddoc}/_view/{view}/queries has been introduced to replace the ?queries parameter formerly provided for making multiple queries to a view. The old ?queries parameter is now deprecated and will be removed in a future release of CouchDB. The maximum http request limit, which had been lowered in 2.1.0, has been re-raised to a 4GB limit for now. (#1446). Ongoing discussion about the path forward for future releases is available in #1200 and #1253. #1118: The least recently used (LRU) cache of databases is now only updated on database write, not read. This has lead to significant performance enhancements on very busy clusters. To restore the previous behaviour, your local ini file can contain the block [couchdb] update_lru_on_read = true. #1153: The CouchDB replicator can now make use of the /_session endpoint rather than relying entirely on HTTP basic authentication headers. This can greatly improve replication performance. We encourage you to upgrade any nodes or clusters that regularly act as replication clients to use this new feature, which is enabled by default (#1462). #1283: The [couchdb] enable_database_recovery feature, which only soft-deletes databases in response to a DELETE /{db} call, is now documented in default.ini. #1330: CouchDB externals and OS daemons are now officially deprecated and no longer documented. Support for these features will be completely removed in a future release of CouchDB (probably 3.0.0). #1436: CouchDB proxy authentication now uses a proper chttpd_auth module, simplifying configuration in local ini files. While this is not a backward- compatible breaking change, it is best to update your local ini files to reference the new {chttpd_auth, proxy_authentication_handler} handler rather than the couch_httpd_auth version, as couch_httpd is in the process of being deprecated completely. #1476, #1477: The obsolete update_notification feature, which was replaced by /{db}/_changes feeds c. CouchDB 1.2, has been completely removed. This feature never worked in 2.0 for databases, only for shards, making it effectively useless.
2019-09-06 11:10:47 +02:00
couchdb/share/www/docs/whatsnew/2.2.html
couchdb/share/www/docs/whatsnew/2.3.html
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
couchdb/share/www/docs/whatsnew/index.html
couchdb/share/www/index.html
Import couchdb-1.0.1 as databases/couchdb. Apache CouchDB is a distributed, fault-tolerant and schema-free document- oriented database accessible via a RESTful HTTP/JSON API. Among other features, it provides robust, incremental replication with bi-directional conflict detection and resolution, and is queryable and indexable using a table-oriented view engine with JavaScript acting as the default view definition language. CouchDB is written in Erlang, but can be easily accessed from any environment that provides means to make HTTP requests. There are a multitude of third-party client libraries that make this even easier for a variety of programming languages and environments. (Based on wip/couchdb.)
2010-09-21 14:11:39 +02:00
man/man1/couchdb.1
share/examples/couchdb/default.ini
share/examples/couchdb/local.ini
Update databases/couchdb to 2.0.0. - The build system embeds the Erlang VM into the package, which means that the PLIST may differ across build systems. Hence why we use a semi-dynamic PLIST here. - That also means that lang/erlang is now a build dependency only. - Include a couch-epmd service for the Erlang Port Mapper Daemon using the embedded binary. - Basic RCD script added. Upstream changes since 1.6.x: - Native clustering is now supported. Rather than use CouchDB replication between multiple, distinct CouchDB servers, configure a cluster of CouchDB nodes. - Futon replaced by brand-new, completely re-engineered Fauxton interface. URL remains the same. - The new Mango Query Server provides a simple JSON-based way to perform CouchDB queries without JavaScript or MapReduce. - Mango selectors can be used in _changes feeds instead of JavaScript MapReduce filters. Mango has been tested to be up to an order of magnitude (10x) faster than JavaScript in this application. - Rewrite rules for URLs can be performed using JavaScript functions. - Multiple queries can be made of a view with a single HTTP request. - Views can be queried with sorting turned off ( sorted=false) for a performance boost. - The global changes feed has been enhanced. It is now resumable and persistent. - New endpoints added (documentation forthcoming): - /_membership shows all nodes in a cluster - /_bulk_get speeds up the replication protocol over low-latency connections - /_node/ api to access individual nodes' configuration and compaction features - /_cluster_setup api to set up a cluster from scratch. - /_up api to signal health of a node to a load-balancer - /db/_local_docs and /db/_design_docs (similar to /db/_all_docs) - "Backend" interface on port 5986 used for specific cluster admin tasks. Of interest are the _nodes and _dbs databases visible only through this interface. - Support added for Erlang/OTP 17.x, 18.x and 19 - New streamlined build system written for Unix-like systems and Microsoft Windows Upgrade Notes - The update sequences returned by the /db/_changes feed are no longer integers. They can be any JSON value. Applications should treat them as opaque values and return them to CouchDB as-is. - Temporary views are no longer supported. - It is possible to have multiple replicator databases. replicator/db config option has been removed. Instead _replicator and any database names ending with the /_replicator suffix will be recognized as replicator databases by the system. - Note that the semantics of some API calls have changed due to the introduction of the clustering feature. Specifically, make note of the difference between receiving a 201 and a 202 when storing a document. - all_or_nothing is no longer supported by the bulk_docs API See full release notes: http://docs.couchdb.org/en/latest/whatsnew/2.0.html
2016-11-16 16:59:28 +01:00
share/examples/couchdb/vm.args
Update databases/couchdb to 2.1.1. couchdb 2.1.1 - CouchDB now supports compilation and running under Erlang/OTP 20.x - The couch_peruser functionality is now really fixed - The cookie domain for AuthSession cookies, used in a proxy authentication configuration, can now be customized via the ini file - It is now possible to modify shard maps for system databases - Due to an Erlang bug (ERL-343), invalid paths can be returned if volumes are mounted containing whitespace in their name (fixed) - The current node's local interface can now be accessed at /_node/_local/{endpoint} as well as at /_node/<nodename>@<hostname>/{endpoint}.- The Dockerfile in the source repository has been retired - Fauxton now uses a version of React with a BSD license. - CouchDB now no longer decompresses documents just to determine their uncompressed size - The design document cache (ddoc_cache) has been rewritten to improve performance - Mango now supports partial indexes - Mango queries can now be paginated - Mango _find accepts an execution_stats parameter - Mango now requires that all of the fields in a candidate index must exist in a query's selector - Other minor improvements. couchdb 2.1.0 - The Mango _find endpoint supports a new combination operator, $allMatch. - New scheduling replicator. - Other minor improvements. See changelog for the 2.1.x branch for more: http://docs.couchdb.org/en/latest/whatsnew/2.1.html
2017-11-07 16:33:27 +01:00
@pkgdir couchdb/erts-${VERSION.erts}/man
couchdb: Upgrade to 2.3.1. Now works with current Erlang. Summary of changes between 2.1.x and 2.3.x are listed below. For a more readable version please see the following URLs: http://docs.couchdb.org/en/latest/whatsnew/2.3.html http://docs.couchdb.org/en/latest/whatsnew/2.2.html http://docs.couchdb.org/en/latest/whatsnew/2.1.html 2.3.x Branch Upgrade Notes #1602: To improve security, there have been major changes in the configuration of query servers, SSL support, and HTTP global handlers: Query servers are NO LONGER DEFINED in the .ini files, and can no longer be altered at run-time. The JavaScript and CoffeeScript query servers continue to be enabled by default. Setup differences have been moved from default.ini to the couchdb and couchdb.cmd start scripts respectively. Additional query servers can now be configured using environment variables: export COUCHDB_QUERY_SERVER_PYTHON="/path/to/python/query/server.py with args" couchdb where the last segment in the environment variable (_PYTHON) matches the usual lowercase(!) query language in the design doc language field (here, python.) Multiple query servers can be configured by using more environment variables. You can also override the default servers if you need to set command- line options (such as couchjs stack size): export COUCHDB_QUERY_SERVER_JAVASCRIPT="/path/to/couchjs /path/to/main.js -S <STACKSIZE>" couchdb The mango query server continues to be enabled by default. The Erlang query server continues to be disabled by default. This change adds a [native_query_servers] enable_erlang_query_server = BOOL setting (defaults to false) to enable the Erlang query server. If the legacy configuration for enabling the query server is detected, that is counted as a true setting as well, so existing configurations continue to work just fine. SSL Support Enabling SSL support in the ini file is now easier: [ssl] enable = true If the legacy httpsd configuration is found in your ini file, this will still enable SSL support, so existing configurations do not need to be changed. HTTP global handlers These are no longer defined in the default.ini file, but have been moved to the couch.app context. If you need to customize your handlers, you can modify the app context using a couchdb.config file as usual. #1602: Also to improve security, the deprecated os_daemons and couch_httpd_proxy functionality has been completely removed ahead of the planned CouchDB 3.0 release. We recommend the use of OS-level daemons such as runit, sysvinit, systemd, upstart, etc. to launch and maintain OS daemons instead, and the use of a reverse proxy server in front of CouchDB (such as haproxy) to proxy access to other services or domains alongside CouchDB. #1543: The node-local (default port 5986) /_restart endpoint has been replaced by the clustered (default port 5984) endpoint /_node/$node/_restart and /_node/_local/_restart endpoints. The node-local endpoint has been removed. #1764: All python scripts shipped with CouchDB, including couchup and the dev/run development cluster script, now specify and require Python 3.x. #1396: CouchDB is now compatible with Erlang 21.x. #1680: The embedded version of rebar used to build CouchDB has been updated to the last version of rebar2 available. This assists in building on non-x86 platforms. #1857: Refuse building with known bad versions of Erlang. 2.2.x Branch Upgrade Notes The minimum supported version of Erlang is now 17, not R16B03. Support for Erlang 21 is still ongoing and will be provided in a future release. The CouchDB replication client can now use the /_session endpoint when authenticating against remote CouchDB instances, improving performance since re-authorization does not have to be performed with every request. Because of this performance improvement, it is recommended to increase the PBKDF2 work factor beyond the default 10 to a modern default such as 10000. This is done via the local ini file setting [couch_httpd_auth] iterations = 10000. Do not do this if an older version of CouchDB is replicating TO this instance or cluster regularly, since CouchDB < 2.2.0 must perform authentication on every request and replication performance will suffer. A future version will make this increased number of iterations a default. #820, #1032: Multiple queries can now be made at the POST /{db}/_all_docs/queries, POST /{db}/_design_docs/queries and POST /{db}/_local_docs/queries endpoints. Also, a new endpoint POST /{db}/_design/{ddoc}/_view/{view}/queries has been introduced to replace the ?queries parameter formerly provided for making multiple queries to a view. The old ?queries parameter is now deprecated and will be removed in a future release of CouchDB. The maximum http request limit, which had been lowered in 2.1.0, has been re-raised to a 4GB limit for now. (#1446). Ongoing discussion about the path forward for future releases is available in #1200 and #1253. #1118: The least recently used (LRU) cache of databases is now only updated on database write, not read. This has lead to significant performance enhancements on very busy clusters. To restore the previous behaviour, your local ini file can contain the block [couchdb] update_lru_on_read = true. #1153: The CouchDB replicator can now make use of the /_session endpoint rather than relying entirely on HTTP basic authentication headers. This can greatly improve replication performance. We encourage you to upgrade any nodes or clusters that regularly act as replication clients to use this new feature, which is enabled by default (#1462). #1283: The [couchdb] enable_database_recovery feature, which only soft-deletes databases in response to a DELETE /{db} call, is now documented in default.ini. #1330: CouchDB externals and OS daemons are now officially deprecated and no longer documented. Support for these features will be completely removed in a future release of CouchDB (probably 3.0.0). #1436: CouchDB proxy authentication now uses a proper chttpd_auth module, simplifying configuration in local ini files. While this is not a backward- compatible breaking change, it is best to update your local ini files to reference the new {chttpd_auth, proxy_authentication_handler} handler rather than the couch_httpd_auth version, as couch_httpd is in the process of being deprecated completely. #1476, #1477: The obsolete update_notification feature, which was replaced by /{db}/_changes feeds c. CouchDB 1.2, has been completely removed. This feature never worked in 2.0 for databases, only for shards, making it effectively useless.
2019-09-06 11:10:47 +02:00
@pkgdir couchdb/erts-${VERSION.erts}/doc
Reference in a new issue Copy permalink