point to docs

andymckay · Dec 8, 2012 · cb021d8 · cb021d8
1 parent 70e7167
commit cb021d8
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 26 deletions.
diff --git a/README.rst b/README.rst
@@ -3,27 +3,6 @@ detection points from OWASP:
 
 https://www.owasp.org/index.php/AppSensor_DetectionPoints
 
-*Note*: this is not really ready for use yet.
+Please docs on:
 
-Setup
------
-
-To install::
-
-        pip install django-paranoia
-
-
-Add in the middleware::
-
-        MIDDLEWARE_CLASSES = (
-                ...
-                'django_paranoia.middleware.Middleware',
-        )
-
-Hook up the reporters in your settings file::
-
-        from django_paranoia import configure
-        configure.config([
-                'django_paranoia.reporters.log',
-                'django_paranoia.reporters.cef_'
-        ])
+https://django-paranoia.readthedocs.org/en/latest/
diff --git a/docs/topics/overview.rst b/docs/topics/overview.rst
@@ -7,7 +7,7 @@ Django Paranoia is a library to try and detect nasty things going on your site.
 It does not prevent attacks, just logs them.
 
 Setup
------
+=====
 
 To install::
 
@@ -32,7 +32,7 @@ If you don't want to pass data through to *config* then you can also set
 *DJANGO_PARANOIA_REPORTERS*, just ensure that *config* is called.
 
 Using
------
+=====
 
 The OWASP Detection points cover a large amount of the Django site, so each
 part is covered in seperately:
@@ -42,7 +42,7 @@ part is covered in seperately:
 * :ref:`views`
 
 Output
-------
+======
 
 When you configure Django Paranoia, you can pass through a list of reporters.
 Current choices are: