CouchDB-v2.x
Apache CouchDB is an open-source, document-oriented NoSQL database that stores data as JSON documents with a simple HTTP/JSON interface, built-in replication,…
Platform availability
Available on 1 of 9 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
12/100 Low
- Maintained
- 0GitHub repository no longer exists
- Popular
- No data
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
Based on 2 of 4 factors.
Availability: platform listings confirmed today, links checked 16 days ago
No GitHub repository data collected yet.
Checked 17 days ago - source: GitHub (apache/docker-couchdb)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 17 days ago - source: Docker Hub image tags and published docs
First-install notes
- Start CouchDB as the couchdb user After setup, run CouchDB from the dedicated couchdb account, for example sudo -i -u couchdb /home/couchdb/bin/couchdb, rather than as root. This avoids permission problems with CouchDB's data files and settings. source
- Set Snap data directories correctly If you use the Snap install, make database_dir and view_index_dir point to /var/snap/couchdb/common/data in the CouchDB config. That folder is where your databases and indexes are stored, so a mismatched path can make CouchDB look for data in the wrong place. source
- Open port 5984 for client access If other apps or browsers on different machines need to reach CouchDB, open port 5984 on your firewall. This is the default web/API port, and blocking it will keep those requests from connecting. source
Fetched 16 days ago - each note links to its source
Variants
Alternatives (9)
- FerretDB - FerretDB is an open-source MongoDB compatibility proxy for self-hosted stacks.
- Microsoft SQL Server - SQL Server delivers on Microsoft’s Data Platform vision by helping your organization manage your data by enabling you to store data from st…
- MongoDB - MongoDB is a cross-platform, open-source document-oriented NoSQL database that stores data in flexible, JSON-like BSON documents instead of…
- MySQL Community Edition - Free GPL database platform supporting SQL and NoSQL applications with InnoDB storage, replication, clustering, connectors, and cross-platfo…
- PostgreSQL - PostgreSQL (Postgres) is an open source object-relational database known for reliability and data integrity.
- RavenDB - RavenDB is an open-source, transactionally consistent document database that stores application data in flexible records, helping developer…
- Redis - Redis is a fast, in-memory data structure store that can be used as a database, cache, and message broker.
- Valkey - Valkey is an open-source, high-performance in-memory key-value datastore forked from Redis.
- mariadb - MariaDB is a fast, open-source relational database server forked from MySQL by its original developers.
Checked 14 days ago - source: AlternativeTo
Common questions
Should the CouchDB service be started as root in a self-hosted setup?
No, run it from a dedicated couchdb account rather than root. This avoids permission problems with CouchDB's data files and settings.
Which port must be reachable for other machines to use the default CouchDB web/API?
Open port 5984 on your firewall. It is the default web/API port, and blocking it prevents client or browser requests from connecting.
Can a single-node CouchDB deployment later be turned into a cluster?
Yes. CouchDB can start as a single node, and more demanding projects can seamlessly upgrade to a cluster.
Is a self-hosted CouchDB instance the preferred backend for the Self-hosted LiveSync plugin?
Yes. The plugin supports various backends, but a self-hosted CouchDB instance is the primary recommended architecture.
If Obsidian LiveSync says CouchDB settings are wrong or suboptimal, can it correct them?
Yes. Obsidian LiveSync can provide buttons to fix the individual config options.
Answers sourced from couchdb.apache.org, deepwiki.com, docs.couchdb.org, docs.couchdb.org, www.reddit.com
Community
- CouchDB - Reddit (reddit)
Collected 11 days ago - public community threads