I want to know how to make static files show up when developing locally.
- Think of some search terms that might describe what you're looking for. Let's go with django static files runserver
- Search Duck Duck Go for django static files runserver
- Optionally search Google (via DDG): !g django static files runserver
- Search Django documentation: !django static files runserver
- Search StackOverflow: !so static files runserver
- If we figure out a better description of our problem while scouring results we'll start again at step 1 using new search terms
If you happen to know an exact spelling/capitalization of what you're looking for in the Django documentation try http://django.me. For example try http://django.me/static
- djangosnippets is a great resource for brief examples and tinn solutions
- Django Packages is very large directory of Django apps
- StackOverflow answers often contain code snippets solving common problems
- StackOverflow answers often contain links to useful Django apps
Some questions to ask:
- Is the code still fresh? Recent activity in the repo might mean yes.
- Does the code have tests?
- Does the code appear to be used by others?
- Is the code clean? Do you understand how the code works?
Some resources you should read:
- Test-Driven Django
- A Guide to Testing in Django
- Writing a Selenim Test Framework for a Django Site
- The Scourge of Slow Tests (and What to Do About It)
- Migrating Django Test Fixtures Using South
- Two Scoops of Django: the book isn't done yet, but it's surprisingly good
Instead of depending on Google to redirect you to one of these blogs, just read the archives now. It could save you a lot of time.
Is nose worth mentioning in testing? It isn't django specific but it is commonly used.
If we are mentioning non-django specific packages what about sphinx for docs.
Other django packages:
Haystack