Build WebUI during Vercel deployment and enforce Cache-Control for admin UI #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
static/adminassets are available on each deploy.index.htmlfrom being served by applying explicit cache semantics at both the application and edge.Description
bash scripts/build-webui.shtovercel.jsonso Vercel runs the WebUI build during deployment.headersrules invercel.jsonto setCache-Control: public, max-age=31536000, immutablefor/admin/assets/(.*)andCache-Control: no-store, must-revalidatefor/admin/(.*)at the edge.routes/home.pyto returnFileResponsewithCache-Controlheaders soassets/files are served with long-term immutable caching and the SPAindex.html(and other non-asset static files) are served withno-store, must-revalidate.Testing
Codex Task