[GH-ISSUE #9] Implement a clean update mechanism #8

Open
opened 2026-03-03 11:13:19 +03:00 by kerem · 2 comments
Owner

Originally created by @debloper on GitHub (Jun 23, 2024).
Original GitHub issue: https://github.com/debloper/xiosk/issues/9

This utility is meant to be "set it and forget it", so no one is forced to update if they're satisfied with how it's working for them. It shouldn't even have to have automated updates, notifying annoying them to update.

But at least for the ones who want to stay at the bleeding edge & update, it shouldn't be more than just one or two scripts to run.

Originally created by @debloper on GitHub (Jun 23, 2024). Original GitHub issue: https://github.com/debloper/xiosk/issues/9 This utility is meant to be _"set it and forget it"_, so no one is forced to update if they're satisfied with how it's working for them. It shouldn't even have to have automated updates, ~~notifying~~ annoying them to update. But at least for the ones who want to stay at the bleeding edge & update, it shouldn't be more than just one or two scripts to run.
Author
Owner

@andiohn commented on GitHub (Jul 30, 2024):

Perhaps on reboot it can add a 'update me' page to the urls it cycles through? Then you log in to the admin portal and push go.

<!-- gh-comment-id:2259337040 --> @andiohn commented on GitHub (Jul 30, 2024): Perhaps on reboot it can add a 'update me' page to the urls it cycles through? Then you log in to the admin portal and push go.
Author
Owner

@debloper commented on GitHub (Aug 1, 2024):

Yes, there are 3 parts to this:

  • check if update is available (compare local vs upstream git tree)
  • show the call to action UX when update is available
  • run update script & reboot to apply changes
<!-- gh-comment-id:2261996960 --> @debloper commented on GitHub (Aug 1, 2024): Yes, there are 3 parts to this: - check if update is available (compare local vs upstream git tree) - show the call to action UX when update is available - run update script & reboot to apply changes
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/xiosk#8
No description provided.