Repository navigation
feat(frontend): add nginx production container - #705
woahwhattheheck wants to merge 4 commits into
Conversation
|
Ready for maintainer review at current head |
|
/claim #539 Original-author GrantFox OSS/FWC26 contribution and conditional compensation claim: I, @woahwhattheheck (GitHub account ID 293286387), submit this original contribution for issue #539 and affirmatively claim contributor credit and consideration for any eligible bounty compensation under the campaign terms. Please confirm eligibility, acceptance criteria, award amount (if applicable), and payment instructions. No award or payment is presumed. |
Closes #539.
What
distoutput in the runtime image.index.htmlwhile keeping missing hashed assets as real 404s.Cache-Control: no-storefor the entry point / SPA fallback and one-year immutable caching for Vite fingerprinted/assets/files.Validation
Exact current head:
e69bc297072c0a5dca9f492130263a086e86a51d, based directly on sponsormain@171c74b454daba241bfb75f36d10a0a3a77a68e5.Fork run 37248045155 completed successfully on that exact head:
nginx -tsucceeded./index.htmlreturnedCache-Control: no-store./dashboardreturned the same SPA entry point withno-store.Cache-Control: public, max-age=31536000, immutable./assets/...path returned 404 and did not receive the immutable cache policy.The other repository workflows that fail immediately on owner-fork pushes are separate zero-job workflow/configuration gates; they are not represented here as frontend-container source failures.