Update Django documentation links to 1.8

Signed-off-by: Michal Čihař <michal@cihar.com>

docs/admin/auth.rst

@@ -233,7 +233,7 @@ To allow access to this project, you have to add the privilege to do so either
 directly to given user or group of users in Django admin interface. Or using
 user management on project page as described in :ref:`manage-acl`.
 
-.. seealso:: https://docs.djangoproject.com/en/1.7/topics/auth/default/#auth-admin
+.. seealso:: https://docs.djangoproject.com/en/1.8/topics/auth/default/#auth-admin
 
 Managing users and groups
 -------------------------

docs/admin/config.rst

@@ -16,7 +16,7 @@ All settings are stored in :file:`settings.py` (as usual for Django).
     Please check also `Django's documentation`_ for parameters which configure
     Django itself.
 
-.. _`Django's documentation`: https://docs.djangoproject.com/en/1.7/ref/settings/
+.. _`Django's documentation`: https://docs.djangoproject.com/en/1.8/ref/settings/
 
 .. setting:: ANONYMOUS_USER_NAME
 

docs/admin/install.rst

@@ -205,7 +205,7 @@ Creating database for Weblate
 It is recommended to run Weblate on some database server. Using SQLite backend
 is really good for testing purposes only.
     
-.. seealso:: :ref:`production-database`, `Django's databases <https://docs.djangoproject.com/en/1.7/ref/databases/>`_
+.. seealso:: :ref:`production-database`, `Django's databases <https://docs.djangoproject.com/en/1.8/ref/databases/>`_
 
 Creating database in PostgreSQL
 +++++++++++++++++++++++++++++++
@@ -253,7 +253,7 @@ options:
     List of site administrators to receive notifications when something goes
     wrong, for example notifications on failed merge or Django errors.
 
-    .. seealso:: https://docs.djangoproject.com/en/1.7/ref/settings/#admins
+    .. seealso:: https://docs.djangoproject.com/en/1.8/ref/settings/#admins
 
 ``ALLOWED_HOSTS``
 
@@ -264,7 +264,7 @@ options:
 
         ALLOWED_HOSTS = ['demo.weblate.org']
 
-    .. seealso:: https://docs.djangoproject.com/en/dev/ref/settings/#std:setting-ALLOWED_HOSTS
+    .. seealso:: https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-ALLOWED_HOSTS
 
 ``SESSION_ENGINE``
 
@@ -283,8 +283,8 @@ options:
     .. seealso:: 
        
         :ref:`database-setup`
-        https://docs.djangoproject.com/en/1.7/ref/settings/#databases, 
-        https://docs.djangoproject.com/en/1.7/ref/databases/
+        https://docs.djangoproject.com/en/1.8/ref/settings/#databases, 
+        https://docs.djangoproject.com/en/1.8/ref/databases/
 
 ``DEBUG``
 
@@ -295,7 +295,7 @@ options:
     Debug mode also slows down Weblate as Django stores much more information
     internally in this case.
 
-    .. seealso:: https://docs.djangoproject.com/en/1.7/ref/settings/#debug
+    .. seealso:: https://docs.djangoproject.com/en/1.8/ref/settings/#debug
 
 ``DEFAULT_FROM_EMAIL``
 
@@ -423,7 +423,7 @@ environment), for example setup for MySQL:
         }
     }
 
-.. seealso:: :ref:`installation`, `Django's databases <https://docs.djangoproject.com/en/1.7/ref/databases/>`_
+.. seealso:: :ref:`installation`, `Django's databases <https://docs.djangoproject.com/en/1.8/ref/databases/>`_
 
 .. _production-cache:
 
@@ -442,7 +442,7 @@ variable, for example:
         }
     }
 
-.. seealso:: :ref:`production-cache-avatar`, `Django’s cache framework <https://docs.djangoproject.com/en/1.7/topics/cache/>`_
+.. seealso:: :ref:`production-cache-avatar`, `Django’s cache framework <https://docs.djangoproject.com/en/1.8/topics/cache/>`_
 
 .. _production-cache-avatar:
 
@@ -469,7 +469,7 @@ recommended to use separate, file backed cache for this purpose:
             },
         }
 
-.. seealso:: :setting:`ENABLE_AVATARS`, :ref:`production-cache`, `Django’s cache framework <https://docs.djangoproject.com/en/1.7/topics/cache/>`_
+.. seealso:: :setting:`ENABLE_AVATARS`, :ref:`production-cache`, `Django’s cache framework <https://docs.djangoproject.com/en/1.8/topics/cache/>`_
 
 .. _production-email:
 
@@ -490,8 +490,8 @@ have correct sender address, please configure ``SERVER_EMAIL`` and
     `DEFAULT_FROM_EMAIL documentation`_,
     `SERVER_EMAIL documentation`_
 
-.. _DEFAULT_FROM_EMAIL documentation: https://docs.djangoproject.com/en/1.7/ref/settings/#default-from-email
-.. _SERVER_EMAIL documentation: https://docs.djangoproject.com/en/1.7/ref/settings/#server-email
+.. _DEFAULT_FROM_EMAIL documentation: https://docs.djangoproject.com/en/1.8/ref/settings/#default-from-email
+.. _SERVER_EMAIL documentation: https://docs.djangoproject.com/en/1.8/ref/settings/#server-email
 
 
 .. _production-hosts:
@@ -502,7 +502,7 @@ Allowed hosts setup
 Django 1.5 and newer require ``ALLOWED_HOSTS`` to hold list of domain names
 your site is allowed to serve, having it empty will block any request.
 
-.. seealso:: https://docs.djangoproject.com/en/dev/ref/settings/#std:setting-ALLOWED_HOSTS
+.. seealso:: https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-ALLOWED_HOSTS
 
 .. _production-avatar:
 
@@ -537,7 +537,7 @@ really use own value rather than using the one coming from example setup.
 You can generate new key using :file:`examples/generate-secret-key` shipped
 with Weblate.
 
-    .. seealso:: https://docs.djangoproject.com/en/dev/ref/settings/#std:setting-SECRET_KEY
+    .. seealso:: https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-SECRET_KEY
 
 .. _production-admin-files:
 
@@ -600,7 +600,7 @@ configure it using following snippet:
         )),
     )
 
-.. seealso:: `Django documentation on template loading <https://docs.djangoproject.com/en/1.7/ref/templates/api/#django.template.loaders.cached.Loader>`_
+.. seealso:: `Django documentation on template loading <https://docs.djangoproject.com/en/1.8/ref/templates/api/#django.template.loaders.cached.Loader>`_
 
 .. _server:
 
@@ -632,7 +632,7 @@ use that for following paths:
 Additionally you should setup rewrite rule to serve :file:`media/favicon.ico`
 as :file:`favicon.ico`.
 
-.. seealso:: https://docs.djangoproject.com/en/1.7/howto/deployment/
+.. seealso:: https://docs.djangoproject.com/en/1.8/howto/deployment/
 
 Sample configuration for Lighttpd
 +++++++++++++++++++++++++++++++++

docs/faq.rst

@@ -121,7 +121,7 @@ database. Please open admin interface and edit default site name and domain
 (you can do that directly at ``/admin/sites/site/1/`` URL under your Weblate
 installation).
 
-.. seealso:: https://docs.djangoproject.com/en/dev/ref/contrib/sites/
+.. seealso:: https://docs.djangoproject.com/en/1.8/ref/contrib/sites/
 
 Why are all commits committed by Weblate <noreply@weblate.org>?
 ---------------------------------------------------------------
@@ -315,7 +315,7 @@ This can happen with SQLite database as it is not powerful enough for some
 relations used within Weblate. The only way to fix this is to use some more
 capable database, see :ref:`production-database` for more information.
 
-.. seealso:: :ref:`production-database`, `Django's databases <https://docs.djangoproject.com/en/1.7/ref/databases/>`_
+.. seealso:: :ref:`production-database`, `Django's databases <https://docs.djangoproject.com/en/1.8/ref/databases/>`_
 
 Features
 ++++++++

weblate/settings_example.py

@@ -309,7 +309,7 @@ else:
 # A sample logging configuration. The only tangible logging
 # performed by this configuration is to send an email to
 # the site admins on every HTTP 500 error when DEBUG=False.
-# See http://docs.djangoproject.com/en/dev/topics/logging for
+# See http://docs.djangoproject.com/en/1.8/topics/logging for
 # more details on how to customize your logging configuration.
 LOGGING = {
     'version': 1,