docs enhancements

README.rst

@@ -21,10 +21,12 @@ Features
 * Easy and simple web interface.
 * Multiple Hosts per user
 * Add own domains / nameservers (public or only for yourself)
-* Supports IP v4 and v6
+* Supports IP v4 and v6, SSL.
+* Login with local or remote accounts (google, github, bitbucket, ...
+  accounts - everything supported by python-social-auth package)
 * Manual IP updates via web interface
-* Shows time since last update via api
+* Shows time since last update via api, whether it used SSL or not
 * Made with security in mind
-* No nagging, no spamming, trying to not annoy users
+* No nagging, no spamming - trying not to annoy users
 * Free and Open Source Software
 * Made with Python and Django

docs/admin.rst

@@ -63,6 +63,11 @@ to the outside world.
 
 Make sure your static files really work.
 
+Since version 1.6, Django has a nice deployment checklist (make sure stuff
+applies to the django version YOU use):
+
+https://docs.djangoproject.com/en/1.6/howto/deployment/checklist/
+
 
 Configuration
 =============
@@ -89,6 +94,7 @@ Users who are in the "staff" group (like the one initially created when creating
 admin interface (see "Admin" in the same menu as "Logout").
 
 But be careful, the Django admin lets you do all sorts of stuff, admins are allowed to shoot themselves.
+Only give Django admin access ("staff" group membership) to highly trusted admins of the service.
 
 
 Software updates / upgrades

docs/project.rst

@@ -15,6 +15,9 @@ The initial version of the nsupdate.info software was developed in 48h in the Dj
 Project site
 ============
 
+Source code repository, issue tracker (bugs, ideas about enhancements, todo,
+feedback, ...), link to documentation is all there:
+
 https://github.com/nsupdate-info/nsupdate.info
 
 

docs/security.rst

@@ -89,12 +89,12 @@ update client also.
 Nameserver Update Key (backend, RFC 2136)
 -----------------------------------------
 
-We currently store this key (which is basically a base64 encoded shared secret)
-"as is".
+We currently store this key (which is basically a base64 encoded shared secret,
+one per dynamic zone) "as is" into the database ("Domain" records there).
 
 This is somehow critical, but also hard to do better - encryption would only
 help very little here as we would need to decrypt the update key before using it,
-so we would need the unlocked key of that encryption mechanism on the same machine.
+so we would need the unlocked decryption key on the same machine.
 
 Make sure no unauthorized person gets that key or he/she will be able to update
 ANY record in the respective zone / nameserver directly (without going over

setup.py

@@ -38,7 +38,7 @@ setup(
     zip_safe=False,
     platforms='any',
     install_requires=[
-        'django >1.5.3, <1.6', # 1.5.3 has the session serializer configurable
+        'django >1.5.3, <1.6',  # 1.5.3 has the session serializer configurable
         'dnspython',
         'south',
         'django-bootstrap-form',