Django 1.4 Development Workflow Using Static Files

Hi again,

Another quick question. I'm still getting used to 1.4 and I've been setting up a remote static file service for the production deployment of my web app. This works just great however it seems a little cumbersome when developing if I want to add fresh image content I have to add it to the project locally, commit and push the changes, deploy to production and collect the static files there before the image is available to the development server...This seems like a very round about way of developing - I must be missing something here although I do not know what? Should I modify the setting.py to change the STATIC_URL value dependent on whether the server is production or development or is there any smarter way?

As ever any advice is much appreciated.

Huw_at1

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/SL1HBsWfETwJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.