commit | de6275101bcf9201061491831cb869f82270eeda | [log] [tgz] |
---|---|---|
author | Serge Bazanski <q3k@hackerspace.pl> | Mon Aug 24 21:17:55 2020 +0000 |
committer | Serge Bazanski <q3k@hackerspace.pl> | Mon Aug 24 21:20:39 2020 +0000 |
tree | 15fd19c5ee8e7cdfb5af4fb9c79c6525007345d0 | |
parent | cdba291e7d0c42544391d8dcf1bc1b5629e933fe [diff] |
matrix: add Telegram bridge appservice. Configuring this one is a bit different from appservice-irc. Notably, there's no way to give it a registration.yaml to overlay on top of a config, se we end up using an init container with yq to do that for us. Also, I had to manually copy the regsitration.yaml in synapse, from /appservices/telegram-prod/registration.yaml to /data/appservices/telegram-prod.jsonnet, in order to make it work with the synapse docker start magic. :/ Otherwise, this is deployed and seems to be working. Change-Id: Id747a0e310221855556c1d280439376f0c4e5ed6
hscloud
is the main monorepo of the Warsaw Hackerspace infrastructure code.
Any time you see a //path/like/this
, it refers to the root of hscloud, ie. the path path/like/this
in this repository. Perforce and/or Bazel users should feel right at home.
For a pleaseant web viewing experience, see this documentation in hackdoc. This will allow you to read this markdown file (and others) in a pretty, linkable view.
See //doc/codelabs for tutorials on how to use hscloud.
If you want to browse the source of hscloud
in a web browser, use cs.hackerspace.pl.
If you want some other help, talk to q3k, informatic or your therapist.
Directories you should care about:
k0.hswaw.net
)Unless noted otherwise, code in hscloud is licensed under the BSD 0-clause license - see COPYING.