csv-metadata-quality-web/app.yaml

runtime: python39
entrypoint: gunicorn -b :$PORT main:app

handlers:
- url: /static/css/v1
  static_dir: static/css/v1
  http_headers:
    Cache-Control: private
app.yaml: Use Python 3.9 Python 3.9 is apparently now generally available. 2021-03-13 13:12:14 +01:00			`runtime: python39`
Use gunicorn to run on Google App Engine See: https://cloud.google.com/appengine/docs/flexible/python/quickstart 2021-03-12 22:10:29 +01:00			`entrypoint: gunicorn -b :$PORT main:app`
app.yaml: Try to serve static CSS directly Google App Engine is currently caching an old version of my CSS, so I am trying to get it to use the correct version. Let's try serving it directly from the filesystem. See: https://cloud.google.com/appengine/docs/standard/php/getting-started/serving-static-files 2021-03-14 09:36:57 +01:00
			`handlers:`
Move style.min.css to css/v1/style.min.css Trying to break Google App Engine's aggressive caching. 2021-03-14 11:04:28 +01:00			`- url: /static/css/v1`
			`static_dir: static/css/v1`
app.yaml: Set Cache-Control header to private for CSS Google App Engine agressively caches stuff. They are currently serving a 24-hour old version of my CSS after multiple updates and re-deploys. Ughhh. From their docs: > After a file is transmitted with a given expiration time, there is > generally no way to clear it out of web-proxy caches, even if the user > clears their own browser cache. Re-deploying a new version of the app > will not reset any caches. Therefore, if you ever plan to modify a > static file, it should have a short (less than one hour) expiration > time. In most cases, the default 10-minute expiration time is > appropriate. The only way to break this for now is to change the CSS directory. In the future I think we have to be sure to set the private cache control header, which lets browsers cache it, but not public CDNs. See: https://cloud.google.com/appengine/docs/standard/python3/how-requests-are-handled 2021-03-14 10:58:57 +01:00			`http_headers:`
			`Cache-Control: private`