specifying a cache value we must not use ALWAYS unless its NO CACHE (#137)

Link to Issue or Message thread

https://github.com/lab-sync/sensor-monitor/pull/83#discussion_r2975365382

Why is this change necessary?

We do want always on the NO CACHE scenarios so that it never caches but for this one where we are trying to make sure it caches we dont want it b/c we could end up caching errors when we dont want that behavior. I missed it when it suggested this change. https://github.com/LabAutomationAndScreening/copier-nuxt-python-intranet-app/commit/420e88bd377e5ef0d955183d3a2159688ceb243d

How does this change address the issue?

Removes the always flag on the nuxt static resources

What side effects does this change have?

N/A

How is this change tested?

N/A

Summary by CodeRabbit

Chores
Adjusted server response header behavior so caching headers are applied more appropriately depending on how assets are served. Static asset responses will now receive caching directives only in the intended response contexts, while proxied responses consistently include caching and related headers to ensure predictable client-side caching behavior.

Usage

To create a new repository using this template:

Create a basic devcontainer either using the Codespaces default or using the file .devcontainer/devcontainer-to-instantiate-template.json from the base template repo
Inside that devcontainer, run python .devcontainer/install-ci-tooling.py to install necessary tooling to instantiate the template (you can copy/paste the script from this repo…and you can paste it in the root of the repo if you want)
Delete all files currently in the repository. Optional…but makes it easiest to avoid git conflicts.
Run copier to instantiate the template: copier copy --trust gh:LabAutomationAndScreening/copier-nuxt-python-intranet-app.git .
Run python .devcontainer/manual-setup-deps.py --only-create-lock --allow-uv-to-install-python to generate the lock file(s)
Stage all files to prepare for commit (git add .)
Run python3 .github/workflows/hash_git_files.py . --for-devcontainer-config-update to update the hash for your devcontainer file
Commit the changes (optional)
Rebuild your new devcontainer

Development

Obtaining the GraphiQL files to bundle

Navigate into the static folder: cd "template/{% if has_backend %}backend{% endif %}/src/static/{% if frontend_uses_graphql %}static{% endif %}/graphiql"
Confirm by viewing the source of a non-altered GraphiQL page that these are the files to download
curl https://unpkg.com/react@18.2.0/umd/react.production.min.js > react.production.min.js
curl https://unpkg.com/react-dom@18.2.0/umd/react-dom.production.min.js > react-dom.production.min.js
curl https://unpkg.com/js-cookie@3.0.5/dist/js.cookie.min.js > js.cookie.min.js
curl https://unpkg.com/graphiql@3.8.3/graphiql.min.css > graphiql.min.css
curl https://unpkg.com/@graphiql/plugin-explorer@1.0.2/dist/style.css > style.css
curl https://unpkg.com/graphiql@3.8.3/graphiql.min.js > graphiql.min.js
curl https://unpkg.com/@graphiql/plugin-explorer@1.0.2/dist/index.umd.js > index.umd.js

Updating from the template

This repository uses a copier template. To pull in the latest updates from the template, use the command: copier update --trust --conflict rej --defaults