RPMs for openSUSE
smox opened this issue · 8 comments
Hello,
I use webhookd on openSUSE (latest leap and tumbleweed). For that I've build a rpm for easier deployment on my machine.
I you are interested, I can contribute this packages or an automated build process (e.g OpenBuildService).
What your thoughts about that?
I think that would be great!
Hello! I am sorry that it takes so long but I have a 3 month old daughter at home and didn't have much time at the moment.
Currently, I am gathering feedback because I want that it comply with the openSUSE Packaging Guidelines. This is the first package I want to publish.
You can look at it here: https://build.opensuse.org/package/show/home:sm0x/webhookd
I hope you like it and find it useful.
If you have questions or you want some changes please feel free to ask.
I am finish.
You can install it using this page: https://software.opensuse.org/download.html?project=home%3Asm0x&package=webhookd
If you have any feedback, please let me know!
Hi Michael, please don't excuse yourself! Your contribution is valuable and parenting is much more important :)
I need to run a VM to test the packaging (my Linux distributions are generally under Debian or Ubuntu). But from the outside it looks great. Anyway, thanks a lot for the work. If you think it's ok I can add it to the installation methods in the documentation.
I personally feel okay with it. It is possible to install it using my home repo.
Currently, I opened an submit request for factory.
I don't know if this will accepted and how long this takes because it is my first package.
If this will be accepted the package is available in the official tumbleweed repositories (zypper in webhookd).
After this I would create a submit request for leap.
What do you think about this WIKI Page?
Are you okay with it if I document it also in the openSUSE WIKI to point out some special things? For example the location of my scripts folder is not really intuitive for newcomers (it is the home folder for system users created by systemd).
It's great! Regarding the feature list, maybe something like this is more explicit:
- Trigger a shell script or executable via HTTP requests
- Passing the HTTP request parameters to the environment context of the script
- Live stream of the execution output
- Send notification after the execution (email or HTTP request)
- Check the request integrity with HTTP Signature methods
- Authenticate the request with Basic Auth and TLS
Much better! I've updated the WIKI and my Home Repository! :)