"Help! My static files aren't working!"
First, have you actually set up your static files on the Web tab?
If yes: examine a specific example.
Let's start with a specific example of a static file that's not working.
You need to identify 3 pieces of information:
The URL which you expect to be able to load the static file from (eg www.mydomain.com/static/path/to/myfile.css)
The path where this file is stored on disk, in your PythonAnywhere account(eg /home/myusername/myproject/assets/path/to/myfile.css)
The relevant static files mapping from the web tab, the values for its URL and path settings (eg: URL
/static/maps to path
By identifying these 3 pieces of information, you may already be able to figure out what the problem is -- the static files mapping should be able to transform the URL to the path on disk, exactly.
The file is missing on disk
The path to the file and the path in the URL don't quite match (eg, there's an extra level of folder hierarchy in one and not the other)
caching -- if you've only just set up the mapping, the old 404 response may be being cached by your browser. Hit Shift+refresh a few times, or try a new browser tab. You may also need to give our distributed filesystem a few seconds to catch up if you've only just added the target file to the disk.
Case-sensitivity -- Both the URL (after the domain name) and the path on disk are case-sensitive. so
Path/To/MyFile.css != path/to/myfile.css.
Your static files mapping is not active yet. You may need to reload your web app.
You've used a relative path instead of an absolute path in the URL (eg 'static/css/myfile.css' instead of '/static/css/myfile.css' -- this will work for some paths on your site but not others. best to use absolute paths everywhere)
If you still can't figure it out, drop us an email to email@example.com.