Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

checking for new updates and/or applying them #64

Open
kir12 opened this issue May 12, 2024 · 2 comments
Open

checking for new updates and/or applying them #64

kir12 opened this issue May 12, 2024 · 2 comments
Labels
enhancement New feature or request has dependency depends on completion of an older issue

Comments

@kir12
Copy link
Collaborator

kir12 commented May 12, 2024

due to the nature of caching with progressive web apps, it can be somewhat difficult to identify if new changes have been posted to a website and to get those changes in-place. For this reason, some system of checking, reminding, and/or automatic updating should be in-place:

  • create a text file with a version number and place it in a folder on the repository that will be packaged by gh-pages: e.g. src, public, etc.
  • Create a class UpdateCheck.tsx that, when subject to some trigger, grabs the same text file directly from the GitHub repo (e.g. via GitHub API?)
    • Compare the text file that's cached and the text file that's pulled down. Display the results in a Bootstrap Modal with corresponding styling (e.g. green for good, red for needs updating)
    • Conditionally display instructions for pulling down the newest version if needed
  • Add an option in the menu to manually run this modal, and automatically run it once on initial page load
    • Always display the modal if manually queued via the menu, but only display the modal on initial page load if a newer version is found

dependent on #62

@kir12 kir12 added enhancement New feature or request has dependency depends on completion of an older issue labels May 12, 2024
@kir12
Copy link
Collaborator Author

kir12 commented May 12, 2024

follow-on optional augment:

  • during the webpage deployment process, inscribe the running deployment's number as a text file via payload onto the page source
  • have the github api read in the number of completed +running deployments and use that as a diff

@kir12
Copy link
Collaborator Author

kir12 commented Jun 9, 2024

new dependency #66

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request has dependency depends on completion of an older issue
Projects
None yet
Development

No branches or pull requests

1 participant