Auto-remapped old django docs to new version. Resolve #3126

docs/source/Setup/Choosing-a-Database.md

@@ -8,7 +8,7 @@ This page gives an overview of the supported SQL databases as well as instructio
  - MySQL / MariaDB
 
 Since Evennia uses [Django](https://djangoproject.com), most of our notes are based off of what we know from the community and their documentation. While the information below may be useful, you can always find the most up-to-date and "correct" information at Django's [Notes about supported
-Databases](https://docs.djangoproject.com/en/dev/ref/databases/#ref-databases) page.
+Databases](https://docs.djangoproject.com/en/4.1/ref/databases/#ref-databases) page.
 
 ## SQLite3 (default)
 

docs/source/Setup/Installation-Upgrade.md

@@ -29,7 +29,7 @@ If you don't have anything you want to keep in your existing game dir, you can j
 - `cd` to your existing 0.9.5-based game folder (like `mygame`).
 - If you have changed `mygame/web`, _rename_ the folder to `web_0.9.5`. If you didn't change anything (or don't have anything you want to keep), you can _delete_ it entirely.
 - Copy `evennia/evennia/game_template/web` to `mygame/` (e.g. using `cp -Rf` or a file manager). This new `web` folder _replaces the old one_ and has a very different structure.
-- It's possible you need to replace/comment out import and calls to the deprecated [`django.conf.urls`](https://docs.djangoproject.com/en/3.2/ref/urls/#url). The new way to call it is [available here](https://docs.djangoproject.com/en/4.0/ref/urls/#django.urls.re_path).
+- It's possible you need to replace/comment out import and calls to the deprecated [`django.conf.urls`](https://docs.djangoproject.com/en/4.1/ref/urls/#url). The new way to call it is [available here](https://docs.djangoproject.com/en/4.0/ref/urls/#django.urls.re_path).
 - Run `evennia migrate`  - note that it's normal to see some warnings here, _don't_ run `makemigrations` even if the system asks you to.
 - Run `evennia start`
 

docs/source/Setup/Running-Evennia.md

@@ -141,7 +141,7 @@ The `evennia` program will also pass-through options used by the `django-admin`.
 
 ```
 
-For (many) more options, see [the django-admin docs](https://docs.djangoproject.com/en/1.7/ref/django-admin/#usage).
+For (many) more options, see [the django-admin docs](https://docs.djangoproject.com/en/4.1/ref/django-admin/#usage).
 
 ## Advanced handling of Evennia processes
 

docs/source/Setup/Security-Practices.md

@@ -36,7 +36,7 @@ In `server/conf/settings.py`:
 If you decide to allow users to upload their own images to be served from your site, special care must be taken. Django will read the file headers to confirm it's an image (as opposed to a document or zip archive), but [code can be injected into an image file](https://insinuator.net/2014/05/django-image-validation-vulnerability/) *after* the headers that can be interpreted as HTML and/or give an attacker a web shell through which they can access
 other filesystem resources.
 
-[Django has a more comprehensive overview of how to handle user-uploaded files](https://docs.djangoproject.com/en/dev/topics/security/#user-uploaded-content-security), but
+[Django has a more comprehensive overview of how to handle user-uploaded files](https://docs.djangoproject.com/en/4.1/topics/security/#user-uploaded-content-security), but
 in short you should take care to do one of two things: 
 
 * Serve all user-uploaded assets from a *separate* domain or CDN (*not* a subdomain of the one you already have!). For example, you may be browsing `reddit.com` but note that all the user-submitted images are being served from the `redd.it` domain. There are both security and performance benefits to this (webservers tend to load local resources one-by-one, whereas they will request external resources in bulk).