Seems I need to run "./manage collectstatic" to apply changes about django-components HOT 5 CLOSED

Well, for now I will be doing this in my supervisord.conf

command=/bin/bash -c "python /code/manage.py collectstatic --noinput; gunicorn --workers 1 --timeout=300 --reload --bind unix:/app.sock app.wsgi"

from django-components.

Could this be the same bug as this? #191

from django-components.

I am not using the development server, so I don't think its related.
I really want to confirm that collectstatic is required to get component changes updated on the server?

from django-components.

I'm afraid I'm not running django_components in production right now, so I don't have any alternative deployment scenario that does not use collectstatic to compare with. Maybe @lemontheme has some insights here?

from django-components.

Hi there. Neither am I at the moment. (Or Django at all for that matter, since my responsibilities have shifted recently.)

In any case, I can confirm that re-running collectstatic upon file changes is the best way if you want all your static files to appear in the same static output directory.

If I recall correctly, this was less of an issue when using the Django dev server. At deployment time, one would run collectstatic once as part of the 'build' process. In terms of DX, it's not perfect, but it lets us re-use builtin Django functionality rather than write extra custom logic.

Does that more or less answer your question? :)

from django-components.