Frontend: configure caching policy in nginx.conf

[giorio94]

Description

This PR enhances the nginx configuration file of the frontend, to introduce directives concerning the caching policy of the different resources. In particular, it enforces non versioned resources are always revalidated with the upstream, while static assets can be freely cached as versioned.

Fixes # (issue)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.

• [X] Locally, checking that resources are correctly cached
• [x] Through the deploy staging environment

[giorio94]

/deploy-staging

[kingmakerbot]

Hi @giorio94. Thanks for your PR.

I am @kingmakerbot. You can interact with me issuing a slash command in the first line of a comment. Currently, I understand the following commands:

• /rebase: Rebase this PR onto the master branch
• /merge: Merge this PR into the master branch
• /hold: Adds hold label to prevent merging with /merge
• /unhold: Removes the hold label to allow merging with /merge
• /deploy-staging: Deploy a staging environment to test this PR (the build-all flag enables user environments building)
• /undeploy-staging: Manually undeploy the staging environment

Make sure this PR appears in the CrownLabs changelog, adding one of the following labels:

• kind/breaking: :boom: Breaking Change
• kind/feature: :rocket: New Feature
• kind/bug: :bug: Bug Fix
• kind/cleanup: :broom: Code Refactoring
• kind/docs: :memo: Documentation

[kingmakerbot]

Your staging environment has been correctly deployed/updated! Available here: Frontend, Qlkube Operators: add the crownlabs.polito.it/operator-selector=staging-783 label to your tenant.

[giorio94]

/merge

[kingmakerbot]

Your staging environment has been correctly teared-down!