-
-
Notifications
You must be signed in to change notification settings - Fork 922
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
Re-add BASE_PATH #1389
Comments
You have to put a process in place to overwrite / mount a different nginx unit config anyway, so there's little reason to include BASE_PATH again in the default config. It's perfectly fine to use an extra.py configuration file for this. So, IMHO, there's no real benefit here. But there is a real drawback, since people will assume that BASE_PATH just works and will be disappointed when it doesn't (and possibly file issues). |
I don't know why you have to overwrite or mount the nginx unit config? Maybe you have something in mind other than I do. I didn't read carefully, but it seems like maybe indeed you can't just load an environment variable in unit/njs?: nginx/unit#968 |
njs itself does seem to have access to environment variables with xref |
Release 2.6.1 ( #1002 ) removed the BASE_PATH variable exposed by netbox-docker (but which exists in upstream netbox) with commit 155e90c because it wasn't sufficient to set up netbox under a different path correctly. #650 (comment) describes how to do it.
The text was updated successfully, but these errors were encountered: