[allura] branch master updated: Improve .ini notes about static caching in production

[br...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

brondsem pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/allura.git


The following commit(s) were added to refs/heads/master by this push:
     new 2324ecf  Improve .ini notes about static caching in production
2324ecf is described below

commit 2324ecfd1ecdb0ffa594a23617242b897b0168ea
Author: Dave Brondsema <da...@brondsema.net>
AuthorDate: Wed Jun 26 18:01:03 2019 -0400

    Improve .ini notes about static caching in production
---
 Allura/production-docker-example.ini | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/Allura/production-docker-example.ini b/Allura/production-docker-example.ini
index 26949b9..a1d2c4c 100644
--- a/Allura/production-docker-example.ini
+++ b/Allura/production-docker-example.ini
@@ -44,8 +44,13 @@ set debug = false
 
 ; Used to uniquify references to static resources, can be a timestamp or any unique value
 ; This should be updated each time you deploy (or make significant changes, like new tools, new css)
+; For example, when you deploy, run this:
+;    sed -i.bak -e "s/^build_key=.*/build_key=`date +%s`/" your-production.ini
 build_key=1276635823
 
+; After you make "build_key" update for every deploy (see above), uncomment this line for static assets to cache for 1 year
+;ew.cache_header_seconds = 31536000
+
 base_url = https://myexamplesite.com
 domain = myexamplesite.com
 site_name = My Example Site