The new CouchDB 3 requires authentication to access the /_all_dbs endpoint.
With our current Upholstery interface we don't want to send a username/password for CouchDB to the end user -- in fact, we'd like to move away from upholstery.
Setting up Sapindale server to have a username/password setup (environment sent to container) would allow us to set up special Sapindale password for access.
Sascha suggested a temporary workaround is to hard-code what databases the tool can support, and we update that array whenever we have a new database that staff need to look at.
The new CouchDB 3 requires authentication to access the /_all_dbs endpoint.
With our current Upholstery interface we don't want to send a username/password for CouchDB to the end user -- in fact, we'd like to move away from upholstery.
Setting up Sapindale server to have a username/password setup (environment sent to container) would allow us to set up special Sapindale password for access.
Sascha suggested a temporary workaround is to hard-code what databases the tool can support, and we update that array whenever we have a new database that staff need to look at.