Update outdated Django docs references

babybuddy/settings/base.py

@@ -352,7 +352,7 @@ AXES_LOCKOUT_URL = "/login/lock"
 
 # Session configuration
 # Used by RollingSessionMiddleware to determine how often to reset the session.
-# See https://docs.djangoproject.com/en/4.0/topics/http/sessions/
+# See https://docs.djangoproject.com/en/5.0/topics/http/sessions/
 
 ROLLING_SESSION_REFRESH = 86400
 

docs/configuration/application.md

@@ -7,7 +7,7 @@
 When in debug mode, Baby Buddy will print much more detailed error information
 for exceptions. This setting should be *False* in production deployments.
 
-See also [Django's documentation on the DEBUG setting](https://docs.djangoproject.com/en/4.0/ref/settings/#debug).
+See also [Django's documentation on the DEBUG setting](https://docs.djangoproject.com/en/5.0/ref/settings/#debug).
 
 ## `SUB_PATH`
 

docs/configuration/database.md

@@ -6,7 +6,7 @@
 
 The database engine utilized for the deployment.
 
-See also [Django's documentation on the ENGINE setting](https://docs.djangoproject.com/en/4.0/ref/settings/#engine).
+See also [Django's documentation on the ENGINE setting](https://docs.djangoproject.com/en/5.0/ref/settings/#engine).
 
 ## `DB_HOST`
 

docs/configuration/security.md

@@ -15,7 +15,7 @@ Do not include schemes ("http" or "https") with this setting.
 
 **See also**
 
-- [Django's documentation on the ALLOWED_HOSTS setting](https://docs.djangoproject.com/en/4.0/ref/settings/#allowed-hosts)
+- [Django's documentation on the ALLOWED_HOSTS setting](https://docs.djangoproject.com/en/5.0/ref/settings/#allowed-hosts)
 - [`CSRF_TRUSTED_ORIGINS`](#csrf_trusted_origins)
 - [`SECURE_PROXY_SSL_HEADER`](#secure_proxy_ssl_header)
 
@@ -26,7 +26,7 @@ Do not include schemes ("http" or "https") with this setting.
 If this is set to `True`, the browser CSRF cookie will be marked as "secure", which instructs the browser to only send the cookie over an HTTPS connection (never HTTP).
 
 **See also**
-- [Django's documentation on the `CSRF_COOKIE_SECURE` setting](https://docs.djangoproject.com/en/4.0/ref/settings/#csrf-cookie-secure)
+- [Django's documentation on the `CSRF_COOKIE_SECURE` setting](https://docs.djangoproject.com/en/5.0/ref/settings/#csrf-cookie-secure)
 
 ## `CSRF_TRUSTED_ORIGINS`
 
@@ -43,7 +43,7 @@ Each entry must contain both the scheme (http, https) and fully-qualified domain
 
 **See also**
 
-- [Django's documentation on the `CSRF_TRUSTED_ORIGINS` setting](https://docs.djangoproject.com/en/4.0/ref/settings/#std:setting-CSRF_TRUSTED_ORIGINS)
+- [Django's documentation on the `CSRF_TRUSTED_ORIGINS` setting](https://docs.djangoproject.com/en/5.0/ref/settings/#std:setting-CSRF_TRUSTED_ORIGINS)
 - [`ALLOWED_HOSTS`](#allowed_hosts)
 - [`SECURE_PROXY_SSL_HEADER`](#secure_proxy_ssl_header)
 
@@ -62,8 +62,8 @@ Baby Buddy modifies headers in the HTTP request; HTTP headers in the request hav
     HTTP_X_AUTH_USER
 
 **See also**
-- [Django's documentation on the `REMOTE_USER` authentication method](https://docs.djangoproject.com/en/4.1/howto/auth-remote-user/)
+- [Django's documentation on the `REMOTE_USER` authentication method](https://docs.djangoproject.com/en/5.0/howto/auth-remote-user/)
-- [Django's documentation on the request.META object](https://docs.djangoproject.com/en/4.1/ref/request-response/#django.http.HttpRequest.META)
+- [Django's documentation on the request.META object](https://docs.djangoproject.com/en/5.0/ref/request-response/#django.http.HttpRequest.META)
 - [`REVERSE_PROXY_AUTH`](#reverse_proxy_auth)
 
 ## `REVERSE_PROXY_AUTH`
@@ -85,7 +85,7 @@ ensure the headers are not forwarded from sources other than your proxy.
 A random, unique string must be set as the "secret key" before Baby Buddy can
 be deployed and run.
 
-See also [Django's documentation on the SECRET_KEY setting](https://docs.djangoproject.com/en/4.0/ref/settings/#secret-key).
+See also [Django's documentation on the SECRET_KEY setting](https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key).
 
 ## `SECURE_PROXY_SSL_HEADER`
 
@@ -98,7 +98,7 @@ came in via HTTPS).
 
 **See also**
 
-- [Django's documentation on the SECURE_PROXY_SSL_HEADER setting](https://docs.djangoproject.com/en/4.0/ref/settings/#secure-proxy-ssl-header)
+- [Django's documentation on the SECURE_PROXY_SSL_HEADER setting](https://docs.djangoproject.com/en/5.0/ref/settings/#secure-proxy-ssl-header)
 - [`ALLOWED_HOSTS`](#allowed_hosts)
 - [`CSRF_TRUSTED_ORIGINS`](#csrf_trusted_origins)
 
@@ -109,4 +109,4 @@ came in via HTTPS).
 If this is set to `True`, the browser session cookie will be marked as "secure", which instructs the browser to only send the cookie over an HTTPS connection (never HTTP).
 
 **See also**
-- [Django's documentation on the `SESSION_COOKIE_SECURE` setting](https://docs.djangoproject.com/en/4.0/ref/settings/#session-cookie-secure)
+- [Django's documentation on the `SESSION_COOKIE_SECURE` setting](https://docs.djangoproject.com/en/5.0/ref/settings/#session-cookie-secure)

docs/contributing/gulp-command-reference.md

@@ -49,7 +49,7 @@ Note: a `SECRET_KEY` value must be set for this command to work.
 
 ### `compilemessages`
 
-Executes Django's `compilemessages` management task. See [django-admin compilemessages](https://docs.djangoproject.com/en/4.0/ref/django-admin/#compilemessages)
+Executes Django's `compilemessages` management task. See [django-admin compilemessages](https://docs.djangoproject.com/en/5.0/ref/django-admin/#compilemessages)
 for more details about other options and functionality of this command.
 
 ### `coverage`
@@ -85,7 +85,7 @@ Executes Python and SASS linting for all relevant source files.
 
 ### `makemessages`
 
-Executes Django's `makemessages` management task. See [django-admin makemessages](https://docs.djangoproject.com/en/4.0/ref/django-admin/#makemessages)
+Executes Django's `makemessages` management task. See [django-admin makemessages](https://docs.djangoproject.com/en/5.0/ref/django-admin/#makemessages)
 for more details about other options and functionality of this command. When
 working on a single translation, the `-l` flag is useful to make message for 
 only that language, e.g. `gulp makemessages -l fr` to make only a French

docs/contributing/translation.md

@@ -47,4 +47,4 @@ Once the translation is complete, commit the new files and changes to a fork
 and [create a pull request](pull-requests.md) for review.
  
 For more information on the Django translation process, see Django's 
-documentation section: [Translation](https://docs.djangoproject.com/en/4.0/topics/i18n/translation/).
+documentation section: [Translation](https://docs.djangoproject.com/en/5.0/topics/i18n/translation/).

docs/setup/deployment.md

@@ -29,7 +29,7 @@ services:
     restart: unless-stopped
 ```
 
-See [Django's databases documentation](https://docs.djangoproject.com/en/4.2/ref/databases/) for database requirements.
+See [Django's databases documentation](https://docs.djangoproject.com/en/5.0/ref/databases/) for database requirements.
 
 See [HTTPS/SSL configuration](ssl.md) for information on how to secure Baby Buddy.
 
@@ -120,7 +120,7 @@ requirements are Python, a web server, an application server, and a database.
 - Python 3.10+, pip, pipenv
 - Web server ([nginx](http://nginx.org/), [Apache](http://httpd.apache.org/), etc.)
 - Application server ([uwsgi](http://projects.unbit.it/uwsgi), [gunicorn](http://gunicorn.org/), etc.)
-- Database (See [Django's databases documentation](https://docs.djangoproject.com/en/4.2/ref/databases/)).
+- Database (See [Django's databases documentation](https://docs.djangoproject.com/en/5.0/ref/databases/)).
 
 ### Example deployment