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

Option to disable built-in updater #254

Open
o-l-a-v opened this issue Jan 2, 2025 · 3 comments
Open

Option to disable built-in updater #254

o-l-a-v opened this issue Jan 2, 2025 · 3 comments
Labels
Core Desktop Enhancement New feature or request

Comments

@o-l-a-v
Copy link

o-l-a-v commented Jan 2, 2025

Use Cases

If one wants to manage Grayjay with a package manager it'd be nice with the ability to disable the built-in updater.

I see no options for this in the GUI or settings.json, nor UpdaterConfig.json.

Proposal

Ideas:

  • Add setting for it that can be toggled in GUI settings, which will be written to settings.json
  • Add switch to the application to not check for updates, can then be added to the shortcut created by the package manager
    • <path_to_grayjay>\grayjay.exe --skip-update-check

References

No response

@o-l-a-v o-l-a-v added the Enhancement New feature or request label Jan 2, 2025
@R-Adrian
Copy link

R-Adrian commented Jan 2, 2025

+1 to an option to have it as manual update check only.

Grayjay v2 has been added to the WinGet package repository... i'm not sure how the automatic updater will handle the case when WinGet will update the app independently.

https://github.com/microsoft/winget-pkgs/tree/master/manifests/f/futo-org/Grayjay/Desktop

@o-l-a-v
Copy link
Author

o-l-a-v commented Jan 2, 2025

Nice. I have a work in progress manifest going for Scoop, but I'm waiting for some things around the updater and non-portable mode to ironed out before I PR it to https://github.com/ScoopInstaller/Extras. This is what I got so far:

@MoralCode
Copy link

MoralCode commented Mar 3, 2025

This would be helpful for #14 since Flatpak would be the mechanism people use to update.

Having an environment variable that disables updating would probably also be a decent method to use for this. If this gets added to the user interface as a toggle-able option, I would hope that the UI would be disabled if the environment variables (or maybe a special read only file placed in the installation directory) suggest that the install is being managed by a package manager

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Core Desktop Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants