[05:14:53] 【Ａｋｔｉｖｉｅｒｅｎ　Ｓｉｅ　ｎｏｃｈ　ｈｅｕｔｅ，　ｕｍ　Ｉｈｒ　Ｒｉｓｉｋｏ　ｚｕ　ｂｅｇｒｅｎｚｅｎ　－　Ａｎｔｉ　Ｖｉｒｕｓ　２０２２】 [05:15:23] http://glx8.mjt.lu/lnk/ [05:19:23] Argh! Wrong channel. I need more coffee! [05:19:25] Sorry [15:10:55] Can a Tool Account be used to host approved bots in a non-English Wikipedia? [15:11:48] su_Theta: yes, toolforge is not limited to any specific wikimedia project, all are good :) [15:52:20] Awesome. Are there maintainers here? Or, where can I find maintainers to talk to? [15:54:18] @su_Theta: maintainers of what specifically? [16:06:04] By maintainer I mean anyone I can ask how I can get access to a Tool Account. [16:09:03] @su_Theta, I'm assuming you've already read this page, no? https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Tool_Accounts [16:09:23] I have. (re @Klein: @su_Theta, I'm assuming you've already read this page, no? https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Tool_Accounts) [16:12:52] @su_Theta: Sorry. I am still a bit confused about what your specific goal is at the moment. I feel that there may be an XY problem () in that you are apparently asking to find maintainers who can give you access to an unspecified tool's account. [16:15:21] It's been a while I've completed my registration myself but if the memory hasn't failed me, you should have been put in a queue or something similar for approval. Did anything of the sort happened? [16:15:27] No. [16:16:06] https://i.ibb.co/94SbTFP/Screenshot-from-2022-05-24-19-16-21.png [16:16:57] That green "Join now" button should give you the form to apply for Toolforge membership. [16:17:04] I think you've just created your WikiTech account but have yet to ask for registration in the ToolForge server judging by your screenshot. [16:17:11] Yes. [16:18:00] !log tools.bridgebot Double IRC messages to other bridges [16:22:01] I made the membership request. Thank you! [16:23:25] @su_Theta: your request is approved! You will need to logout and log back in at https://toolsadmin.wikimedia.org/ for your new permissions to become active. [16:23:40] Wow, that was fast! [16:23:45] You're welcome and welcome! hahha [16:24:38] I certainly can't guarantee service this quick always ;) [16:39:31] One question. Shouldn't we edit `~/.bashrc` as it says `THIS FILE IS MANAGED BY PUPPET`? [16:42:56] if you want a permanent edit in .bashrc you can have that or ask for it by uploading a change to the puppet repo [16:43:18] and yea, if you manually edit it puppet will revert that change on next run [16:43:32] mutante: that's not actually true in Toolforge [16:43:48] ok then, ignore what I said [16:43:50] the "managed by puppet" is about the skel directory [16:44:23] I have installed https://deno.land. Its executable should be added to `$PATH` on every shell login. What's the best way to automate this? [16:45:04] @su_Theta: you should be able to edit things in your $HOME (and also your tool account's $HOME) and have those edits persist. [16:45:23] Alright! [21:40:04] bd808: I did a thing because chicocvenancio said it might be cool https://phabricator.wikimedia.org/F35173745 [21:40:14] should be in the next version of this mwcli tool thingy [21:40:44] how many assumptions about my local ssh client and config does that make? [21:41:24] It just uses rsync and ssh, so it assumes your ssh config is setup correct for the host login.toolforge.org [21:42:24] It could perhaps do with another command to help users setup their ssh config if they don't specify a user I guess. Or perhaps it needs something a little different [21:42:56] does it work from windows? [21:43:11] it works from WSL, let me try for this old cmd.exe thing [21:43:38] * bd808 only asking annoying questions because he assumes that someone will ask here later [21:43:47] * addshore is liking the questions [21:44:11] I meam, without checking, yes it should work if you have ssh and rsync as executables in your windows PATH [21:44:23] otherwise it'll give you a message saying you need them, for each command [21:46:04] * bd808 tracked down the MR at https://gitlab.wikimedia.org/repos/releng/cli/-/merge_requests/189/diffs [21:47:09] * addshore makes a windows release to try it [21:50:15] I believe it should work, but I dont have my ssh configured in windows land :D [21:53:16] *nod* so assuming that something like `ssh login.toolforge.org -- hostname -f` already works for you locally, this would let you run ssh commands and rsyncs to tools. [21:53:43] yes [21:54:34] I imagine a command to help users setup their ssh config could be useful, maybe, but thats a bit of scope creep for this version [21:55:20] nearly all of the tech support requests for ssh things are from Windows + PuTTY users so... make that work ;) [21:56:04] So windows and ssh should work, windows also should come with an ssh agent by default now etc for keys [21:56:39] putty on the other hand.... well... [21:57:06] I guess the putty UI allows folks to specify the username and key in that UI, then magically does the right things? [21:58:15] in which case I guess yeah, either 1) a command to help folks make an ssh-config for tools or 2) more flags that allow you to specify a user and key location [22:18:33] bd808: the only way for users to connect is with ssh keys nower days right? [22:22:18] * addshore reads https://wikitech.wikimedia.org/wiki/Help:Access_to_Toolforge_instances_with_PuTTY_and_WinSCP [22:22:37] addshore: yes. we don't enable interactive (password) auth [22:27:42] * addshore thinks about what a wizard for ssh config creation might look like [22:27:49] minimally I guess a user, and location of an ssh key [22:27:57] though its more complex for folks using an agent I guess [22:39:08] addshore: its probably more work than the value that folks will get from it to be honest. unless you want the challenge for fun I would advise ignoring my poke about it. ;) [22:39:25] xD we will see :) [23:01:37] that sounds like it won’t work for me, then (re @wmtelegram_bot: It just uses rsync and ssh, so it assumes your ssh config is setup correct for the host login.toolforge.org) [23:02:29] ooooh, I dont even know where this one mirrors to :D [23:02:47] want me to add you on the telegram side? ^^ [23:03:01] Yeah! [23:03:35] o/ [23:03:57] @lucaswerkmeister how do you have things set up? [23:04:20] my toolforge ssh config starts with `Host toolforge \n HostName login.toolforge.org` [23:04:30] because why would I want to type `ssh login.toolforge.org` when I can just `ssh toolforge` :P [23:05:03] aaah, so you can't ssh to login.toolforge.org at all as the user wouldn't be set for example? [23:05:20] yeah, nor the IdentityFile [23:06:02] I have something like Host tools login.toolforge.org \n HostName login.toolforge.org [23:06:14] huh [23:06:27] You can specify multiple Hosts to match on line 1 [23:06:30] I didn’t know you could do that [23:06:32] useful [23:06:33] :D [23:06:51] actually it is even longer xD [23:07:11] -dev and -dev-buster? ^^ [23:07:42] actually, ones in other places are longer [23:08:32] I don't think mwcli should cater to folks magic shortened host names ;) but good to know there is an easy solution for your case! [23:15:16] ircs://irc.libera.chat/wikimedia-cloud, https://t.me/wmcloudirc, and https://chat.wmcloud.org/wikimedia/channels/wikimedia-cloud -- all of them are linked from https://wikitech.wikimedia.org/wiki/Help:Cloud_Services_communication (re @wmtelegram_bot: ooooh, I dont even know where this one mirrors to :D)