Sunshine: improve update checks

Open
#101 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
desktop

Research direction

Start by reviewing the Sunshine repository and the linked system-tray discussion (LizardByte discussions/674) to understand the existing update-check and tray behavior. The requested scope includes interval checks, system-tray notifications, a per-session duplicate-notification mechanism, a custom command, and manual tray checks; done means these behaviors are supported.

Written by the indexing model from the issue text.

Description

1-3 months C++ effort:Medium LizardByte/Sunshine planned priority:Medium Rest API
Is there an existing issue for this item?
  • I have searched the existing issues
Repositories

LizardByte/Sunshine

Languages/Skills/Technologies

C++, Rest API

Description

Currently, a user is only notified of a new Sunshine version if they open the web-ui. This can be improved.

  • Check for updates on an interval, and:
    • Display a system tray notification
    • Run a custom command (similar to a prep command), where the user could do whatever they want... such as send a discord webhook, email, etc.
  • Allow manually checking for updates from the system tray (https://github.com/orgs/LizardByte/discussions/674)

If a system tray notification, we need to have a mechanism to not send the same notification more than once (per session).

Estimated Effort

effort:Medium

Priority

priority:Medium

Target Milestone

1-3 months

Dependencies

No response

Dominant language
No language data
Stars
2
Forks
0
Avg merge
25m
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LizardByte/roadmap

All issues in LizardByte/roadmap

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.