Our static files support is an optional extra. If you're happy letting your web framework serve static files for you, then that's fine. Or if you want to you can give the job of serving static files to our web servers, by setting up a static files mapping -- it should mean your web worker has more time for non-static requests, the ones that actually need code.
Static files config is basically a mapping from a URL to a directory. You tell
us where your files are (eg
/home/me/myapp/static), and what URL you want
them served at (eg
/static/) and then hit "Reload web app". Then, any files
inside the static folder will be served, eg
/home/me/myapp/static/css/base.css will appear at
A worked example
Supposing you have some static files stored like this:
/home/myusername/myproject └── assets ├── css │ ├── base.css │ └── bootstrap.css ├── images │ ├── img1.jpg │ └── img2.png └── js └── widgets.js
And, supposing in one of your templates, you want to use some of your static assets, like this:
The two things to note are:
- The URLs all start with
- The path to the place where all your static files are stored is
So, what you want is a static files mapping that says:
The URL /static/ should map to the folder /home/myusername/myproject/assets
Hopefully you can see how, after that, the relative paths are the same?
So now you know what to put in the two boxes on the Static files section in the web tab. Remember to hit "reload" when you're done. To test it, visit the URL of one of your static files directly. Remember to use Ctrl+F5 to force a reload of the page.