webhook

Hookdoo: SaaS that allows you to create incoming webhook endpoints to run shell scripts on your remote servers. https://www.hookdoo.com/ And of course my open-source webhook server project: https://github.com/adnanh/webhook

Hookdoo: SaaS that allows you to create incoming webhook endpoints to run shell scripts on your remote servers. https://www.hookdoo.com/ And of course my open-source webhook server project: https://github.com/adnanh/webhook

Shameless plug: I wrote an open source incoming webhook server that can run your build & redeployment scripts: https://github.com/adnanh/webhook

For those interested in technically easy webhook consuming endpoint server check out https://github.com/adnanh/webhook

Webhook: https://github.com/adnanh/webhook Self hosted tiny incoming webhook server with powerful options. Lets user run shell commands on incoming webhook. Has context parsing (use values from payload, query string, headers etc...). Can use context to validate the requests (i.e. only trigger if the push is coming from GitHub and the ref branch is the master branch). More info can be found in the Readme and on the wiki. Tech stack: Golang --- Hookdoo - https://www.hookdoo.com/ A SaaS spin on the webhook server. Sort of an opposite approach. Has all the features webhook has, and also implements concurrency management (i.e. only run one script and deny others until it's done, allow parallel runs etc...). Centralized, managed, leverages SSH. No need for the user to install and configure anything on their servers. Tech stack: Ruby, Golang, Re

Found it: https://github.com/adnanh/webhook I like it, but isn't it too complicated? Perhaps it would be better to write a small Python (Flask?) app for each kind of webhook you would be accepting, since you're going to run all this in your own server, with your own scripts and your own messy paths. I've tried this in the past: https://github.com/fiatjaf/requesthub.xyz, but the comment above also applies.

https://github.com/adnanh/webhook Incoming webhook server

Hello HN, I am soon launching my first paid SaaS product and I would love to improve my landing page to be more informative and relevant. The SaaS product is targeting a very specific audience so my current version of the landing page[1] assumes that the user knows what a (web)hook is. I am an author of an open-source self hosted tool named webhook[2] and it has validated that the problem I had, others have as well and that there are users who need an incoming server that would execute their code. Main problems with my open-source tool is that managing all these hooks is PITA. If you have more than 5 hooks, you'll start getting lost in your JSON configuration. Providing a web interface in the open-source tool would clash with my philosophy of doing one thing and doing it well. Additionally, I would like to monetize this, and that's the r

https://github.com/adnanh/rye - simple url-catcher on our slack channel (live at http://rye.hajdarevic.net/) (Using slack outgoing webhooks + https://github.com/adnanh/webhook for catching the webhook and running a simple shell script that parses the slack message and extracts all URLs and then hits rye with curl to store and crawl them) https://github.com/adnanh/mikro - my personal micro blog that I mainly use to store interesting links (live at http://blog.hajdarevic.net/) I'm currently working with a friend of mine on an MVP that we plan to offer as a service, and the source code is not open, but the stack is: React (JSX + ES6 + Webpack) + Tachyons for frontend, Ruby (Grape + Sequel) for frontend API, Golang for workers and processing, PostgreSQL as a DB and Redis for caching