Skip to content

Add cache busting for token UI deploys (/token and /tokentest) #48

Description

@dnlbui

Summary

Deploy scripts bump CONFIG.APP.VERSION, but that value currently only updates the visible header label. It does not reliably force browsers to load new JS/CSS after deploy.

Affects:

  • /token
  • /tokentest

Deploy scripts:

  • update-token-client.sh
  • update-tokentest.sh

Problem

index.html loads assets with static URLs, e.g.:

  • ./css/base.css
  • ./js/app.js

No query-string versioning or reload check exists (unlike /farm, which uses version.html + version-check.js).

After deploy, users may continue running cached JS/CSS until a hard refresh.

Possible approaches

Option A — Query-string cache busting

Append version to asset URLs in index.html, e.g. ./js/app.js?v=0.0.11

  • Could be applied during deploy script rewrite
  • Or injected from config.js for module entry only (limited coverage)

Option B — Farm-style version check

Add version.txt / version.html + small reload-on-change script

  • Proven pattern elsewhere in this repo

Option C — Both

  • Version file for reload detection
  • Query strings for individual assets

Acceptance criteria

  • After deploy, a normal page refresh loads updated JS/CSS
  • Works for both /token and /tokentest
  • Deploy scripts remain simple to run locally
  • Approach documented briefly in script headers or repo notes

Priority

Medium

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions