I’m not sure this belongs in the Node.js SDK section as I don’t see that the SDK will help me here, but maybe someone can point out how it can.
For Node, I’d suggest either using the REST API (with Swagger, see this post), or using PouchDB.
Replication doesn’t make sense without a local store, which would point toward using PouchDB. That brings up the question of whether you really need the data local, or if the REST API suites your scenario. Can you describe your use? We’re trying to understand how to prioritize a JS version, so feedback on what you’re doing would be valuable.
I’ll try and give you an idea of what we’re trying to accomplish. We already have Couchbase Lite running in a mobile environment which connects to Couchbase Server. Users have access to a file which can be changed simultaneously using the Sync Gateway. At one point we wanted the ability for a User to copy one of these files. We accomplished this by opening a one-shot pull replicator, getting all the data, creating a new database and then entering the documents back into the new database thus generating a reasonable copy.
Is this enough for you to go on or can I clarify any points?
The mobile application is not where the issue lies. From the mobile app, we can use Couchbase Lite to open Replicators and perform any actions we want.