-
Notifications
You must be signed in to change notification settings - Fork 225
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
Fauxton only works went mounted to url "/",. #944
Comments
Any guide how to properly solve this problem? |
I'll look into this this weekend |
@garrensmith or @Antonio-Maranhao, some urls are registered as apiurl and other as server (we call this one to access couch). We use the apiurl for the raw json query. As I am in the process to review the routes, I would like to replace This way, we could simply control the base url in the settings.json 🎉 |
It would be great if Fauxton can determine where it's hosted automatically. Imagine hosting CouchDB behind a reverse proxy that places all URLs under |
By default, it would use relative path. For example, if you access Fauxton from |
Making Fauxton use a relative path would be awesome but don't replace apiurl. The apiurl is used for the little json button on the top right so that a user can see the api endpoint. |
@garrensmith But does that have to be hard-coded at compile time, or can it be dynamically calculated based on runtime information? If the latter I'm all thumbs up :) |
It can be calculated dynamically. We can just look at window.location for the info
…________________________________
From: Joan Touzet <[email protected]>
Sent: Monday, April 30, 2018 6:34:31 PM
To: apache/couchdb-fauxton
Cc: garren smith; Mention
Subject: Re: [apache/couchdb-fauxton] Fauxton only works went mounted to url "/",. (#944)
@garrensmith<https://github.com/garrensmith> But does that have to be hard-coded at compile time, or can it be dynamically calculated based on runtime information? If the latter I'm all thumbs up :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#944 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAK9AsPXs1v9rpK0yMhSFYhTDVHepO1hks5ttz0XgaJpZM4OnZo_>.
|
Yeah, basically, I calculate the absolute urls with the window.location.href and the relative url. PR should be landing today or tomorrow. |
Great! Will this change be included in a snapshot installed from apt-get? |
It will be included in the next point release of CouchDB (2.2.0) in the official packages. |
Is the old Futon GUI still available in CouchDB2 somehow? We can't upgrade due to this bug unfortunately. |
@lichtamberg No, Futon is no longer supported. Recommend you wait until 2.2.0. |
Thanks for your feedback, is there an ETA when the 2.2.0 will be finished? There are still some bugs open, so I don't know whow long it will take for it to get released? |
Closing this since it has been fixed with #1078. |
@lichtamberg @DQvsRA Any chance you can test the RC for CouchDB 2.2 and see if it works as expected? |
I would love to, but I'm not sure how to install it? I'm just using the normal debian package? |
@lichtamberg you'll need to build from source |
When will it be available for downloading via package managers? |
@ceremcem When CouchDB 2.2.0 RC3 will be accepted. Test of this release candidate would be appreciated ! |
I'm using Fauxton with Express, and when mounted say at url "/db".. everything fails..
Expected Behavior
When mounted at say '/db', request should be '/db/_session',..
Current Behavior
Instead of say requests like -> '/db/_session', the console is showing requests like -> '/_session'
Possible Solution
Make the fauxton route path configurable.
code like ->
This is assuming we have everything running at '/'..
Steps to Reproduce (for bugs)
Run Fauxton from a route like "/db"
Context
I'm trying to make an express app, that can host website, and fauxton etc. Assuming everything is @ "/" is not ideal. So a request say for session would be '/db/_session'
Your Environment
Node
Windows
The text was updated successfully, but these errors were encountered: