Hi guys, I'd like to gather some opinions on ticket #2445 before actually starting to code. Basically the idea is to extend the `manage.py check` command, adding the ability to test connections to remote services your project depends on.
Here's the plan so far: Add a `remote` kwarg to the `checks.register()` decorator Extend the `manage.py check` with a `--remotes` option, which tests *only* connectivity, skipping any other checks. Add some actual connection checks to the core: Database SMTP server Cache Document this feature Notify the popular modules' authors that they could make use of a new feature (Celery is the example that comes to my mind) My key concerns are: Do we have another, more beatiful way instead of adding the kwarg? Dealing with two separate check "dimensions" (deployment, remote) would be a mess. What specific checks should be shipped with the core? Shall we make the connections test skip other checks, or maybe just make the connection-related ones the warnings? Here's the link to the ticket for your convenience: https://code.djangoproject.com/ticket/24475 <https://code.djangoproject.com/ticket/24475> Thanks! — Regards, Alex Morozov -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/F7DDB135-3E5F-45E5-A715-8ADCAF82F107%40mail.ru. For more options, visit https://groups.google.com/d/optout.
