602 karma · joined July 24, 2012
[LinkedIn] https://linkedin.com/in/adnan-h/
[Github] https://github.com/adnanh/
And of course my open-source webhook server project: https://github.com/adnanh/webhook
It also adds the concurrency control feature so you don't have to worry if you want only one instance of the script running, or want to kill the currently running one, or run them in parallel etc...
Another feature would be generic trigger rules where you can use values from payload to see if the script should be run at all (i.e. push to the feature branch, but you want to run the script on merges to master...).
As a developer, all of this might sound easy to implement, but whatever you make, you also have to maintain... And as you know, the business requirements tend to change quite often and you'll get to a point where you have to generalize your custom CGI scripts, and you end up spending more time maintaining infrastructure than doing development on the actual product.
Webhook on other hand is pretty much a CGI server with a few handy features :-)
And of course my open-source webhook server project: 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, Redis, PostgreSQL, ES6 + React
Incoming webhook server
Webhook can wait for the script execution and return the stdout & stderr as response.
It is also possible to wait for the command to finish and return the response as part of the HTTP response, or just return 200 Ok and run the script in the background.
- versioning
- consistency in naming
- documentationOne example would be scenario where you can't remember some word, and you decide you can't remember it and stop thinking about it, your brain continues to search for it in the background (subconsciously)... and then the word comes to you like an interrupt.
I had the same thing with studying for exams (I would dream of the lecture notes and when I wake up in the morning I can perfectly recall everything).
There was a study posted at HN where not completing a task at work, leaves your brain working on it even after you leave your office, only to have the solution pop up in the middle of the night.
All of this can be a result of a stress. You need to take a vacation and relax. Recharge your batteries or you'll be feeling drained really soon...
1 in the morning after my breakfast 2 during the work day (one usually around noon (sometimes I skip this one) and one after lunch) 1 after I come home from work before dinner (sometimes I skip this one)
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
I try to avoid JavaScript if possible... Setting up the JavaScript build/transpile system, installing dependencies, fighting the dependency version hell drains all the hype and productivity from my soul...