Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CouchDB connection request does ignore subfolders in Server URL field #19

Open
thrdroom opened this issue Jan 10, 2023 · 4 comments
Open
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@thrdroom
Copy link

The Bug:
Im running couchdb behind an nginx reverse proxy which is exposed via a subfolder:

example: https://mydomain.com/mycouchdb/

Database name is mynicedb
Username is myusername

when i try to connect nomie to the couchdb i enter https://mydomain.com/mycouchdb/ as my server url, and mynicedb as my database name.

Nomie then gives an error NetworkError when attempting to fetch resource because nomie does try to connect via the following url https://mydomain.com/mynicedb. It does completely ignore the subfolder /mycouchdb/ from the server url field.

Expected behaviour:
Nomie should honor subfolders in the server url field.

@donalmacanri donalmacanri added the bug Something isn't working label Jan 11, 2023
@donalmacanri
Copy link
Collaborator

donalmacanri commented Jan 11, 2023

Can you try entering https://mydomain.com as your server url and mycouchdb/mynicedb as your database name?

@donalmacanri donalmacanri added the question Further information is requested label Jan 11, 2023
@thrdroom
Copy link
Author

Can you try entering https://mydomain.com as your server url and mycouchdb/mynicedb as your database name?

yes, this way was actually my workaround to get the app running. The issue should still be addressed for new users, who don't know how to debug the error message.

@donalmacanri
Copy link
Collaborator

Perhaps it would be less confusing to have a single text field for the full CouchDb URL (instead of having a separate field for database name)?

@thrdroom
Copy link
Author

Perhaps it would be less confusing to have a single text field for the full CouchDb URL (instead of having a separate field for database name)?

No, i think that would be even more confusing if users would have to figure out how to structure the URL correctly.
The "database name" field itself is fine, and not really confusing. But the field should just be used for the databasename and not parts of the "Server URL". The problem is that the "Server URL" field does strip away everything from an URL that comes after the first / behind the domains tld-ending.

The filter of the "Server URL" has to be modified to respect subdirectories that are put into the field and not only the domain name and domainending.

@donalmacanri donalmacanri added documentation Improvements or additions to documentation and removed question Further information is requested labels Jan 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants