package and run notifico #9
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Include this:
22b582fad6
Is the notifico bot supposed to run on nixbld?
Yes.
Work started in
7cffd4f
. Next up: NixOS integration.I've added the service to nixbld in the master branch. Two steps remain for you:
Create a local
/etc/nixos/secret/notifico.py
forservices.notifico.config
(Defaults)Setup a new DNS entry for the HTTP Vhost
notifico.m-labs.hk
(which is not a name that is nice to type in my opinion...)Tell me if I should spend more time on an elaborate UWSGI setup like we have for mattermost-github-integration.
hooks.m-labs.hk
configuration.nix
(e.g. Hydra enables MySQL) - can redis be moved into the notifico pkg?In case you really prefer path mangling over creating DNS entries, we could put both services under
hooks.m-labs.hk
. I have uncommitted changes for that on the Nix side, but there is more to do, at least:SERVER['hook']
to/mattermost-github/
.Do you really want this instead of just another DNS entry?
Done in
5f5aa32341
.Both mattermost-github-integration and notifico warn about using the default dev server and recommend running under UWSGI for stability and performance.
I'm not sure if we have these requirements. I have given it a try but realized we cannot run Notifico in NixOS' standard UWSGI service because it requires Python 2 unlike mattermost-github-integration.
I tried hack-patching Notifico so it runs with Python 3, but there are some bugs, such as all the hooks failing and returning 404.
This thing is quite a beast, requiring 4 processes (web server, bots, worker, redis) and lots of dependencies (some of them outdated just like python2) just to post notifications to IRC...
I wonder if there are simpler and better-maintained alternatives.