Debug server reload after code changes about apistar HOT 6 CLOSED

Django's runserver plus uses watchman

http://django-extensions.readthedocs.io/en/latest/runserver_plus.html#introduction

I believe we should go with that (as livereload has a dependancy on tornado, that I'd rather avoid)

Aside: Hadn't realised that flask's lovely debugging tools are actually part of werkzeug.
We should take advantage of that.

from apistar.

We're not leveraging all the stuff that werkzeug provides right now either...
Eg. Using werkzeug request and response objects might be something we want to do.

from apistar.

Yup, we may do. Will also need to consider similar issues eg. Do templates and static files reload?

from apistar.

Presumably we'd want to use livereload, as we already do with mkdocs...

https://github.com/mkdocs/mkdocs/blob/master/requirements/project.txt

Any other options? Pull requests welcome.

from apistar.

werkzeug has two backends for reloader support, the default is stat and the other one is watchdog not watchman as far as I remember. I agree that actually bringing in werkzeug has a couple of advantages, including the reloader and debugging stuff

from apistar.

Thanks @jpadilla! Been looking into it now.

from apistar.