Documentation overhaul

docs/maintenance/troubleshooting.md

@@ -1,13 +1,5 @@
 # Troubleshooting
 
-## Something broken? Stuck on an issue? Can't get it set up?
-
-Start by checking the [issues](https://gitlab.com/allianceauth/allianceauth/issues?scope=all&utf8=%E2%9C%93&state=all&search=my+issue) - especially closed ones.
-
-No answer?
- - open an [issue](https://gitlab.com/allianceauth/allianceauth/issues)
- - harass us on [gitter](https://gitter.im/R4stl1n/allianceauth)
-
 ## Logging
 
 In its default configuration your auth project logs INFO and above messages to myauth/log/allianceauth.log. If you're encountering issues it's a good idea to view DEBUG messages as these greatly assist the troubleshooting process. These are printed to the console with manually starting the webserver via `python manage.py runserver`.
@@ -32,8 +24,10 @@ Make sure the background processes are running: `supervisorctl status myauth:`.
 
 Stop celery workers with `supervisorctl stop myauth:worker` then clear the queue:
 
+```bash
     redis-cli FLUSHALL
     celery -A myauth worker --purge
+```
 
 Press Control+C once.
 
@@ -50,3 +44,15 @@ This is likely due to a permissions mismatch. Check the setup guide for your web
 ### Unable to execute 'gunicorn myauth.wsgi' or ImportError: No module named 'myauth.wsgi'
 
 Gunicorn needs to have context for its running location, `/home/alllianceserver/myauth/gunicorn myauth.wsgi` will not work, instead `cd /home/alllianceserver/myauth` then `gunicorn myauth.wsgi` is needed to boot Gunicorn. This is handled in the Supervisor config, but this may be encountered running Gunicorn manually for testing.
+
+### Specified key was too long error
+
+Migrations may about with the following error message:
+
+```bash
+Specified key was too long; max key length is 767 bytes
+```
+
+This error will occur if one is trying to use Maria DB prior to 10.2.x, which is not compatible with Alliance Auth.
+
+Install a never Maria DB version to fix this issue another DBMS supported by Django 2.2.