Is this repo dead?

[bdombro]

There haven't been any releases in over a year and PRs are not being reviewed. Should this repo be archived?

[garethbowen]

As long as it's useful it should remain. I think the real question is does anyone actually use it?

[bdombro]

Good question! I have asperations to possibly use it in the far future in hobby projects -- but nothing concrete. I feel like it could be useful if someone wanted to fork or extend a JS flavor of couch bc they like JS.

[garethbowen]

As the README says...

PouchDB Server is much less battle-tested than CouchDB

I would warn against using this for the server for anything that matters. It's really useful for testing or prototyping though...

[respectTheCode]

I am considering an app that would have an Electron "server" app but the main interface would be a web page available on the local network. The app would never have more than a couple of users at a time. Would this be an appropriate use case?

[SourceR85]

Hi @respectTheCode, prefer CouchDB even for local applications.

PouchDB is (like Gareth highlighted) less battle-tested.
This is a rewording of: "you can't rely on it".

The benefit of pouchdb-server is it's capability of running as a "throw-away" server to test your app or expectations against a CouchDB api (and even in this field: it isn't feature complete to CouchDB v3).

[respectTheCode]

I ended up building something custom around SQLite. PouchDB was great but requiring end users to install CouchDB was just not realistic.

[SourceR85]

Hi @respectTheCode, you're welcome to contribute to PouchDB-Server if your customers rely on it.

[kuncevic]

As the README says...

PouchDB Server is much less battle-tested than CouchDB

I would warn against using this for the server for anything that matters. It's really useful for testing or prototyping though...

@garethbowen I believe such a message must be a bit clear and more visible. However, by looking at the latest release date one may assume of the risks using it in prod