Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatic rebuild on ./manage.py runserver #88

Open
sils opened this issue Dec 2, 2016 · 5 comments
Open

Automatic rebuild on ./manage.py runserver #88

sils opened this issue Dec 2, 2016 · 5 comments

Comments

@sils
Copy link

sils commented Dec 2, 2016

Is it possible to have the automatic rebuild of the assets running on ./manage.py runserver?

See also http://webassets.readthedocs.io/en/latest/script.html#watch , CC @userzimmermann

@miracle2k
Copy link
Owner

Something like this could possible be created, but it doesn't exist yet. We wouldn't be the first ones to want to overwrite the "runserver" command, so I think it's possible, though potentially also confusing, if other extensions try to do the same thing.

@userzimmermann
Copy link

@miracle2k Couldn't this be also achived by some Middleware that does the rebuilding on every request automatically when in DEBUG = True mode? It's just a sontaneous thought... I'm not that familiar with the middleware stuff...

CC @sils

@miracle2k
Copy link
Owner

We have that already. It's called ASSETS_AUTO_BUILD. The "watch" command improves on that by not waiting until the request comes in; the idea is that this would reduce the wait time on page refresh.

@userzimmermann
Copy link

@miracle2k And what about a websocket? Which is opened by a special assets URL. Then handles the watch in the backend. And additionally informs the user about the rebuild actions in the frontend...

@miracle2k
Copy link
Owner

It's possible to build something like this. It doesn't exist at this time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants