Update documentation to allow removal of wiki pages.

docs/maintenance/cloudflare.md

@@ -1,41 +0,0 @@
-# CloudFlare
-
-CloudFlare offers free SSL and DDOS mitigation services. Why not take advantage of it?
-
-## Setup Protection
-
-You’ll need to register an account on [CloudFlare’s site.](https://www.cloudflare.com/)
-
-Along the top bar, select `Add Site`
-
-Enter your domain name. It will scan records and let you know you can add the site. Continue setup.
-
-On the next page you should see an A record for yourdomain.com pointing at your server IP. If not, manually add one:
-
-    A    yourdomain.com     my.server.ip.address     Automatic TTL
-
-Add the record and ensure the cloud under Status is orange. If not, click it. This ensures traffic gets screened by CloudFlare.
-
-If you want forums or kb on a subdomain, and want these to be protected by CloudFlare, add an additional record for for each subdomain in the following format, ensuring the cloud is orange:
-
-    CNAME     subdomain         yourdomain.com       Automatic TTL
-
-CloudFlare blocks ports outside 80 and 443 on hosts it protects. This means, if the cloud is orange, only web traffic will get through. We need to reconfigure AllianceAuth to provide services under a subdomain. Configure these subdomains as above, but ensure the cloud is not orange (arrow should go around a grey cloud).
-
-## Redirect to HTTPS
-
-Now we need to configure the https redirect to force all traffic to https. Along the top bar of CloudFlare, select `Page Rules`. Add a new rule, Pattern is yourdomain.com, toggle the `Always use https` to ON, and save. It’ll take a few minutes to propagate.
-
-![infographic](http://i.stack.imgur.com/VUBvo.jpg)
-
-## Update Auth URLs
-
-Edit settings.py and change the following values:
- - FORUM_URL = `os.environ.get('AA_FORUM_URL', "http://forums.mydomain.com")` if forums are on a subdomain
- - IPBOARD_ENDPOINT = `os.environ.get('AA_IPBOARD_ENDPOINT', 'http://forums.mydomain.com/ipboard/interface/board/index.php')` if forums are on a subdomain
- - JABBER_URL = `os.environ.get('AA_JABBER_URL', "jabber.yourdomain.com")`
- - OPENFIRE_ADDRESS = `os.environ.get('AA_OPENFIRE_ADDRESS', "http://jabber.yourdomain.com:9090")`
- - MUMBLE_URL = `os.environ.get('AA_MUMBLE_URL', "mumble.yourdomain.com")`
- - TEAMSPEAK3_PUBLIC_URL = `os.environ.get('AA_TEAMSPEAK3_PUBLIC_URL', 'ts.yourdomain.com')`
-
-And there we have it. You’re DDOS-protected with free SSL.

docs/maintenance/index.md

@@ -6,6 +6,5 @@
 
     changelog
     troubleshooting
-    cloudflare
 
 ```

docs/maintenance/troubleshooting.md

@@ -3,7 +3,6 @@
 ## Something broken? Stuck on an issue? Can't get it set up?
 
 Start here:
- - read the [documentation](https://github.com/R4stl1n/allianceauth/wiki)
  - check the [issues](https://github.com/R4stl1n/allianceauth/issues?utf8=%E2%9C%93&q=is%3Aissue) - especially closed ones
  - check the [forums](https://forums.eveonline.com/default.aspx?g=posts&t=383030)
 
@@ -16,9 +15,7 @@ No answer?
 
 ### `pip install -r requirements.txt` is failing
 
-Most commonly, your repositories did not include the `requests` package. Install it and try again: `sudo pip install requests`
-
-Otherwise it's usually a missing dependency. Check [the list](../installation/auth/dependencies.md), reinstall, and try again.
+Either you need to `sudo` that command, or it's a missing dependency. Check [the list](../installation/auth/dependencies.md), reinstall, and try again.
 
 ### I'm getting an error 500 trying to connect to the website on a new install
 
@@ -26,7 +23,11 @@ Read the apache error log: `sudo nano /var/log/apache2/error.log`
 
 If it talks about failing to import something, google its name and install it.
 
-If it whines about being unable to configure logger, make sure the log directory is write-able: `chmod -R 777 /home/allianceserver/allianceauth/log`, then reload apache.
+If it whines about being unable to configure logger, see below. 
+
+### Failed to configure log handler
+
+Make sure the log directory is write-able: `chmod -R 777 /home/allianceserver/allianceauth/log`, then reload apache/celery/supervisor/etc.
 
 ### Groups aren't syncing to services
 
@@ -34,9 +35,7 @@ Make sure the background processes are running: `ps aux | grep celery` should re
 
 If that doesn't do it, try clearing the worker queue. First kill all celery processes as described above, then do the following:
 
-    sudo rabbitmqctl stop_app
-    sudo rabbitmqctl reset
-    sudo rabbitmqctl start_app
+    redis-cli FLUSHALL
     python manage.py celeryd --purge
 
 Press control+C once.