Files changed (4)
-If you feel that you might be cluttering your settings.py with all these ``HOPTOAD_*`` settings, you can conveniently group them in a dictionary::
+There are more advanced options that can be used to customize your Hoptoad_ notification process; please go to `Configuration guide <http://sjl.bitbucket.org/django-hoptoad/config/>`_ to see more advanced configuration and usage options.
+If you desire to use SSL and your account plan supports it, then you can use the following setting to enable SSL POSTs:
+This will force all HTTP requests to use SSL. There's always a possibility, due to either an account downgrade, or, an expiration of a SSL certificate that Hoptoad might return an error code of `402` on a POST. There is built-in support automatically to try to re-POST the same error message without using SSL. To enable this feature, just add this option as well:
+On a highly trafficked website, there is a noticeable degree of a delay when POST'ing to hoptoad -- either due to error limitations, network instability, or other acts of God that can cause an HTTP request to slow down or fail. To fix this, django-hoptoad will spawn a daemon thread, by default, that will spawn a thread pool, with 4 threads, to queue up all errors for maximum throughput. However, this can be configured to your heart's content, including changing the notification handler completely.
+To control the number of threads spawned per threadpool, you can set the following variable to your desired thread count per threadpool:
+There is also built-in support for various other methods of communicating **synchronously** with Hoptoad, and that requires just one more setting:
+> This is the default setting. Will return a daemonized thread with a 4 worker-thread thread pool to handle all enqueued errors.
+> This will switch from the thread pool approach to a blocking HTTP POST where the entire Django process is halted until this blocking call returns.
+What if you do not want to use any of the default handlers, but instead, use your own proprietary system?
+There is support for drop-in replacements of handlers so that you might write your own custom handler. More documentation on this to follow.
+Currently, Hoptoad has their notification URLs pointed to `http://hoptoadapp.com/notifier_api/v2/notices`, but this has been the second time that this was changed. It, therefore, can be expected that this will change again, so it is configurable like so:
+As you've probably noticed, these hoptoad settings are getting to be extremely abundant, so in order to give you some organization support for your `settings.py`, we've included support for grouping them in a dictionary. You can group them using `HOPTOAD_SETTINGS` as a dictionary and django-hoptoad will have support for this:
If you're having trouble you might want to take a look at the [Troubleshooting Guide][troubleshooting].