[05:47:13] !log melos@tools-bastion-13 tools.stewardbots SULWatcher/manage.sh restart # SULWatchers disconnected [05:47:15] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.stewardbots/SAL [11:33:30] email notifications are working fine, I got the email about https://wikitech.wikimedia.org/w/index.php?title=User:Lucas_Werkmeister/sandbox&diff=prev&oldid=2294603 right away [12:53:28] Hi, is it possible to tools-db database be a replication slave of an external mariadb server? [13:56:19] nokibsarkar: not with the current setup, what is your use case? [14:02:08] I have a tool hosted on digitalocean droplet (sponsored by WLF). I want to create a replication backup on tools db. [14:03:35] I think we could try doing that in a Trove database, but not in toolsdb [14:10:30] as replication slave? [14:24:30] !log lucaswerkmeister@tools-bastion-13 tools.ranker deployed 37e5987b2b (l10n updates: fr) [14:24:32] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.ranker/SAL [14:26:15] nokibsarkar: yes I never tried but I think it might work [14:27:19] technically it could be possible with toolsdb as well, but toolsdb is shared by hundreds of tools and I don't want to risk any issue [14:27:43] with Trove we can be more experimental [14:30:54] Is there any automated ways to create a GitLab group under cloudvps-repos? As T387060 is not done yet, I am looking for a project to use GitLab-managed OpenTofu state. [14:33:19] no [14:33:39] (T387062 proposes retiring that namespace entirely) [14:33:39] T387062: Retire /cloudvps-repos, merge to /repos - https://phabricator.wikimedia.org/T387062 [14:34:16] you might want to poke -releng about T387060, which has been open for a while [14:34:17] T387060: Create new GitLab project group: wmgmc - https://phabricator.wikimedia.org/T387060 [14:38:38] How can I "poke" them? [15:06:53] xtex: one way is on IRC in the channel #wikimedia-releng [15:07:56] dhinus: thanks! [15:09:14] xtex: here are other options https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Contact [15:10:44] tburm: thank you!