and deploying Processes and ports Running behind a load balancer Static files and aggressive file caching Debug mode and automatic reloading WSGI and Google App Engine Introduction Tornado [http://www template_loader application setting. Compiled templates are cached by default; to turn off this caching and reload templates so changes to the underlying files are always visible, use the application settings $scheme; proxy_pass http://frontends; } } } Static files and aggressive file caching You can serve static files from Tornado by specifying the static_path setting in your application:

template_loader application setting. Compiled templates are cached by default; to turn off this caching and reload templates so changes to the underlying files are always visible, use the application settings proxy_set_header X-Scheme $scheme; proxy_pass http://frontends; } } } Static files and aggressive file caching You can serve static files from Tornado by specifying the static_path setting in your application: You can configure almost any web server to recognize the version tags used by static_url() and set caching headers accordingly. Here is the relevant portion of the nginx configuration we use at FriendFeed:

template_loader application setting. Compiled templates are cached by default; to turn off this caching and reload templates so changes to the underlying files are always visible, use the application settings } 6.1. User’s guide 37 Tornado Documentation, Release 6.0.4 Static files and aggressive file caching You can serve static files from Tornado by specifying the static_path setting in your application: You can configure almost any web server to recognize the version tags used by static_url() and set caching headers accordingly. Here is the relevant portion of the nginx configuration we use at FriendFeed:

and deploying Processes and ports Running behind a load balancer Static files and aggressive file caching Debug mode and automatic reloading WSGI and Google App Engine Introduction Tornado [http://www template_loader application setting. Compiled templates are cached by default; to turn off this caching and reload templates so changes to the underlying files are always visible, use the application settings $scheme; proxy_pass http://frontends; } } } Static files and aggressive file caching You can serve static files from Tornado by specifying the static_path setting in your application:

Tornado Documentation, Release 4.5.3 Compiled templates are cached by default; to turn off this caching and reload templates so changes to the underlying files are always visible, use the application settings proxy_set_header X-Scheme $scheme; proxy_pass http://frontends; } } } Static files and aggressive file caching You can serve static files from Tornado by specifying the static_path setting in your application: You can configure most any web server to recognize the version tags used by static_url() and set caching headers ac- cordingly. Here is the relevant portion of the nginx configuration we use at FriendFeed:

template_loader application setting. Compiled templates are cached by default; to turn off this caching and reload templates so changes to the underlying files are always visible, use the application settings proxy_set_header X-Scheme $scheme; proxy_pass http://frontends; } } } Static files and aggressive file caching You can serve static files from Tornado by specifying the static_path setting in your application: You can configure almost any web server to recognize the version tags used by static_url() and set caching headers accordingly. Here is the relevant portion of the nginx configuration we use at FriendFeed:

template_loader application setting. Compiled templates are cached by default; to turn off this caching and reload templates so changes to the underlying files are always visible, use the application settings proxy_set_header X-Scheme $scheme; proxy_pass http://frontends; } } } Static files and aggressive file caching You can serve static files from Tornado by specifying the static_path setting in your application: can con- figure almost any web server to recognize the version tags used by static_url() and set caching headers accordingly. Here is the relevant portion of the nginx configuration we use at FriendFeed:

template_loader application setting. Compiled templates are cached by default; to turn off this caching and reload templates so changes to the underlying files are always visible, use the application settings proxy_set_header X-Scheme $scheme; proxy_pass http://frontends; } } } Static files and aggressive file caching You can serve static files from Tornado by specifying the static_path setting in your application: can con- figure almost any web server to recognize the version tags used by static_url() and set caching headers accordingly. Here is the relevant portion of the nginx configuration we use at FriendFeed:

template_loader application setting. Compiled templates are cached by default; to turn off this caching and reload templates so changes to the underlying files are always visible, use the application settings proxy_set_header X-Scheme $scheme; proxy_pass http://frontends; } } } Static files and aggressive file caching You can serve static files from Tornado by specifying the static_path setting in your application: can con- figure almost any web server to recognize the version tags used by static_url() and set caching headers accordingly. Here is the relevant portion of the nginx configuration we use at FriendFeed:

template_loader application setting. Compiled templates are cached by default; to turn off this caching and reload templates so changes to the underlying files are always visible, use the application settings proxy_set_header X-Scheme $scheme; proxy_pass http://frontends; } } } Static files and aggressive file caching You can serve static files from Tornado by specifying the static_path setting in your application: can con- figure almost any web server to recognize the version tags used by static_url() and set caching headers accordingly. Here is the relevant portion of the nginx configuration we use at FriendFeed: