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

Script execution as alternative to notification #36

Open
juk0de opened this issue Nov 12, 2023 · 1 comment
Open

Script execution as alternative to notification #36

juk0de opened this issue Nov 12, 2023 · 1 comment

Comments

@juk0de
Copy link

juk0de commented Nov 12, 2023

I've just stumbled upon #3 and #1 and I thought: why not simply execute a user provided script if an update is available? Then the user can decide if they want to send a mail, try an automated update or do something completely different.

Each software entry could take an optional script path to be executed. The script should accept the new version nr. and release download URL as arguments. Would be easier to implement than #1 and #3 and also more flexible imho...

@juk0de juk0de changed the title Script execution as alternative to notfication Script execution as alternative to notification Nov 12, 2023
@franok
Copy link
Owner

franok commented Nov 12, 2023

Hey @juk0de
a User-Provider script is a great idea. Agree that it would replace #1 and #3 (or leave the decision to the user).

I would not see a user provided script this alternative, but additional/optional step after sending a notification. Or, if you see this as requirement: provide an additional parameter per software entry sendGotification that enables/disables the gotify notification sending, per software.

So I see two features in this:

  1. user provided script as additional, optional step
  2. toggle to disable notifications individually per software entry.

Unfortunately I currently do not find time to implement this.
However I can offer to review pull requests if you like to implement one (or both) of the features :-).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants