couchapp | The official repo is now at http

I deployed a Node application to CouchDB that I developed and built from a Vue Webpack template. One of the modules I rely on, pdfjs-dist, relies on a worker.

After running npm run build and getting my output in dist, I copy the output files to couchapp to deploy them to CouchDB. I get no errors during deployment and the site looks fine once it's up.

However, when I try doing something that requries pdfjs-dist, I get the error:

NetworkError: Failed to load worker script at "http://.../docuapp/documentation/_design/uploads/static/js/app.4eb1aecbadc78360a76e.worker.js" (unbekannt) Error: Loading chunk 0 failed. Stack-Trace: u@http://.../docuapp/documentation/_design/uploads/static/js/manifest.a6f78538bddeebdefd4a.js:1:957 manifest.a6f78538bddeebdefd4a.js:1:1378 Error: Loading chunk 0 failed. manifest.a6f78538bddeebdefd4a.js:1:957

So I check out the url that's failing to load, and the document is missing. But when I remove the worker part of the url, i.e.

Before installing the CouchApp utility, the Sofa blog app and the sample DB myblogdb together with CouchDB 2.1.1 my CouchDB was working find and I never seeing any Internal Server Error.

In the last 2 hours a trojan attached itself as a process to the CouchDB. Since then I removed it, but it might have jammed some of the CouchDB's settings.

Why can't I run myblogdb? Does this error have something to do with the breaking changes caused by upgrade to CouchDB 2.1.1?

Firstly, couchapp push myblogdb only works on second attempt (first attempt ends in Internal Server Error):

I'm creating a single page CouchApp, using _attachments to serve the JavaScript application directly from CouchDB. I've set up a vhost to db/_design/ddoc/_rewrite to achieve this.

The data in the database can only be viewed by certain users in the _users database, which is achieved by adding them as members to the db/_security document.

I would like the single page application, which has PouchDB packaged, to take control of fetching data, and performing authentication by means of pouchdb-authentication. Herein lies the problem: I cannot access the application before authenticating.

That leads me to my question; Is there a way to expose the _attachments in a design document to unauthenticated users, without granting everybody access to the rest of the database? Currently I'm weighing toward storing my app in a separate database without any members, but I would prefer to use a single database and work it out with the permission system in place.

I am working in a project using CouchDB CouchBase lite and Android. I want to use a filter function so I am doing on my server end :

I am trying to work with CouchDB filtering but I can not understand how it works

So lets say, like the example they have:

I am creating a CouchApp and have a question about remote databases and creating a PouchDB object.

• The CouchApp is available from htps://subdomain.website.com/
• The CouchDB instance is on htps://username.cloudant.com/database
• I use a rewrite rule in the database
• There is a Virtual Host from subdomain.website.com to username.cloudant.com/database/_design/client/_rewrite
• I am not using replication, only a direct connection

I currently create a new PouchDB object using:

var db = new PouchDB('htps://username.cloudant.com/database');

But I would rather instantiate it as:

var db = new PouchDB('/database');

or

var db = new PouchDB('database');

My guess is that PouchDB sees this as a local database instead of a remote database. Is my thinking correct, and how can I get my desired result? I want to strip the hostname of the URL because I want to keep everything portable and replicate it over other servers.