cubicweb #13144242 Improve reload mechanism in cubicweb-ctl pyramid --debug [open]

When developing views in cubicweb using pyramid, the reload functionality is great, but reloading everything can be a bit long on some applications or some dev environments. It would be nice to have a better refresh time for this usecase (might be split into separate tickets) :

  • keep listening to the port so that a refresh in the browser doesn't end up with "Unable to connect", even if the reload is long, one refresh is enough
  • reload only parts of the application (by configuration, or by which files have changed)

Will post another issue about a page reloader driven by websocket as we often find in the NPM stack.

done in<not specified>
closed by<not specified>