I actually meant this as a developer question: as, at least in my review of
the code, and testing with `manage.py runserver`. use of `SCRIPT_NAME` has
no observable effect.
If that can be confirmed, then yes, the documentation should be updated,
and I can do a PR accordingly. Use of `SCRIPT_NAME`
Hi Arthur,
You've found the wrong mailing list for this thread. This mailing list is
for discussing the development of Django itself, not for support using
Django. I guess that's why no one replied.
If you would like to suggest a documentation change please do open a PR
with reference to the info
I found https://code.djangoproject.com/ticket/7930 seems like
`FORCE_SCRIPT_NAME` just isn't meant to work.
Maybe the docs should reflect that.
Arthur Pemberton
On Fri, Jun 16, 2023 at 5:18 PM Arthur Pemberton wrote:
> Even with `FORCE_SCRIPT_NAME` `MEDIA_URL` is being prefixed properly, but
Even with `FORCE_SCRIPT_NAME` `MEDIA_URL` is being prefixed properly, but
not `STATIC_URL` .
Was `FORCE_SCRIPT_NAME` just not meant to be used with the `runserver` ?
Arthur Pemberton
On Fri, Jun 16, 2023 at 5:01 PM Arthur Pemberton wrote:
> The docs reference `FORCE_SCRIPT_NAME` but say very
