matrix-docker-ansible-deploy

コミットグラフ

作成者	SHA1	メッセージ	日付
Julian-Samuel Gebühr	05c1333ebb	Restrict permissions of container	4年前
Julian-Samuel Gebühr	07cfd3ba09	Use custom invocation instead of provided script	4年前
Julian-Samuel Gebühr	64fbc5ff87	Replace spaces with tabs	4年前
Julian-Samuel Gebühr	7baf477c16	Remove unnecessary variable The /data is hardcoded in the container	4年前
Julian-Samuel Gebühr	2f167f2122	Rename docker container to matrix-bot-maubot	4年前
Julian-Samuel Gebühr	6ed105b830	Rename service from matrix-maubot to matrix-bot-maubot	4年前
Julian-Samuel Gebühr	d5c82a5221	Remove logging to /var/log and make readonly	4年前
Julian-Samuel Gebühr	0ea146930b	Make exposing management UI configurable	4年前
Julian-Samuel Gebühr	4d40b61a51	Fix config error, add nginx	4年前
Julian-Samuel Gebühr	1316656998	Rename to bot_maubot and fix permission error	4年前
Julian-Samuel Gebühr	d24cb7db6f	Initial maubot commit	4年前
Slavi Pantaleev	0364c6c634	Suppress old container cleanup (kill/rm) failures People often report and ask about these "failures". More-so previously, when the `docker kill/rm` output was collected, but it still happens now when people do `systemctl status matrix-something` and notice that it says "FAILURE". Suppressing to avoid further time being wasted on saying "this is expected".	4年前
Slavi Pantaleev	86c36523df	Replace ExecStopPost with ExecStop Reverts b1b4ba501fdfaa, 90c9801c560b6, a3c84f78ca9c65a, .. I haven't really traced it (yet), but on some servers, I'm observing `ansible-playbook ... --tags=start` completing very slowly, waiting to stop services. I can't reproduce this on all Matrix servers I manage. I suspect that either the systemd version is to blame or that some specific service is not responding well to some `docker kill/rm` command. `ExecStop` seems to work great in all cases and it's what we've been using for a very long time, so I'm reverting to that.	4年前
rakshazi	d7af37e9e9	matrix-bot-honoroit feedback	4年前
rakshazi	407e8c4940	added honoroit	4年前

6 コミット (27b1835ed47af91b253ab3d399b030a833641cf2)