CouchDB Weekly News, June 19

Releases

Apache CouchDB 1.6.0 released

This is a feature release. Download link | Release notes

Blog Posts

Major Discussions

How to get the BigCouch Merge + Fauxton running for testing (see thread)

How to get the BigCouch branch and Fauxton running for testing. The detailed description can be found here. Please help us with the tests, and post any bugs you notice to dev@ Mailing List. Your help is highly appreciated.

Releases in the CouchDB Universe

Opinions and other News in the CouchDB Universe

Use Cases, Questions and Answers

no public answer yet:

For more new questions about CouchDB, see these search results.

Get involved!

If you want to get into working on CouchDB:

  • We have an infinite number of open contributor positions on CouchDB. Submit a pull request and join the project!
  • Here’s a list of beginner tickets around our currently ongoing Fauxton-implementation. If you have any questions or need help, don’t hesitate to contact us in the couchdb-dev IRC room (#couchdb-dev) – Garren (garren) and Sue (deathbear) are happy to help.

We’d be happy to have you!

Events

Job opportunities for people with CouchDB skills

… and also in the news

Apache CouchDB 1.6.0 Released

Apache CouchDB 1.6.0 has been released and is available for download.

CouchDB is a database that completely embraces the web. Store your data with JSON documents. Access your documents with your web browser, via HTTP. Query, combine, and transform your documents with JavaScript. CouchDB works well with modern web and mobile apps. You can even serve web apps directly out of CouchDB. And you can distribute your data, or your apps, efficiently using CouchDB’s incremental replication. CouchDB supports master-master setups with automatic conflict detection.

Grab your copy here:

http://couchdb.apache.org/

Pre-built packages for Windows and OS X are available.

CouchDB 1.6.0 is a feature release, and was originally published on 2014-06-10.

These release notes are based on the changelog.

Upgrade Notes

The Proxy
Authentication
handler was renamed to proxy_authentication_handler to follow the
*_authentication_handler form of all other handlers. The old proxy_authentification_handler
name is marked as deprecated and will be removed in future releases. It’s strongly recommended
to update the httpd/authentication_handlers
option with the new value if you have this handler configured.

What’s New

  • COUCHDB-2200: support Erlang/OTP 17.0 #35e16032
  • Fauxton: many improvements in our experimental new user interface, including
    switching the code editor from CodeMirror to Ace as well as better support
    for various browsers.
  • Add the max_count option (UUIDs Configuration) to allow rate-limiting
    the amount of UUIDs that can be requested from the /_uuids
    handler in a single request (CVE 2014-2668).
  • COUCHDB-1986: increase socket buffer size to improve replication speed
    for large documents and attachments, and fix tests on BSD-like systems.
    #9a0e561b
  • COUCHDB-1953: improve performance of multipart/related requests.
    #ce3e89dc
  • COUCHDB-2221: verify that authentication-related configuration settings
    are well-formed. #dbe769c6
  • COUCHDB-1922: fix CORS exposed headers. #4f619833
  • Rename proxy_authentification_handler to proxy_authentication_handler.
    #c66ac4a8
  • COUCHDB-1795: ensure the startup script clears the pid file on termination.
    #818ef4f9
  • COUCHDB-1962: replication can now be performed without having write access
    to the source database (#1d5fe2aa), the replication checkpoint
    interval is now configurable (#0693f98e).
  • COUCHDB-2025: add support for SOCKS5 proxies for replication.
    #fcd76c9
  • COUCHDB-1930: redirect to the correct page after submitting a new document
    with a different ID than the one suggested by Futon. #4906b591
  • COUCHDB-1923: add support for attachments and att_encoding_info options
    (formerly only available on the documents API) to the view API.
    #ca41964b
  • COUCHDB-1647: for failed replications originating from a document in the
    _replicator database, store the failure reason in the document.
    #08cac68b
  • A number of improvements for the documentation.