Add option to serve with URL prefix #2008
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added the option to run Doccano with a URL prefix instead of always running from the domain root. The prefix is configured by specifying a
BASE_URL
environment variable. This PR fixes #1878To run Doccano under
/doccano/
, setBASE_URL
to/doccano/
:export BASE_URL=/doccano/
When we now compile the front-end, all routes are prefixed with BASE_URL.
We also need to let Django know about our new prefix. This is done using the same BASE_URL environment variable but needs to be set during runtime. I could not find a clean method to configure them both during runtime.
Since such a configuration will most likely only be used in combination with a load balancer, I also added the option to set
USE_X_FORWARDED_HOST
using environment variables.Note that I did not write any tests for this (yet), both because I am unsure how this should be done and because I would first like to know if this PR would be acceptable.