User talk:DCaro (WMF)

Welcome to Toolforge!

Hello David Caro, welcome to the Toolforge project! Your request for access was processed, and you should be able to use ssh to connect to login.toolforge.org. You will need to logout and login again at https://toolsadmin.wikimedia.org/ to activate your new permissions there.

Check the Toolforge help page for tips on using your account. You can also ask questions in our IRC channel at #wikimedia-cloud ^connect or send an e-mail to our mailing list cloud@lists.wikimedia.org.

Thank you, and have fun making Tools! --StrikerBot (talk) 13:53, 2 November 2020 (UTC)

Wikimedia Hackathon Northwestern Europe 2026

Hello! I came across your name on a previous Wikimedia hackathon participant page, so I thought you might be interested in this.

We're organizing the Wikimedia Hackathon Northwestern Europe 2026, taking place on 13–14 March 2026 in Arnhem, the Netherlands. It's a two-day, in-person hackathon for technical Wikimedians from the region.

Since you've attended a hackathon before, you already know how valuable these events can be for collaboration, learning, and getting things done together. We'd love to have you join us!

Apply here – registration closes mid-January or when full.

Feel free to reach out if you have any questions. Hope to see you in Arnhem! Daanvr (talk) 14:59, 12 January 2026 (UTC)

Webservice on Toolforge

Hello. Two years ago you helped me to transfer my webservice from grid to k8s using buildservice-created image. You advised me to switch from CGI/C#/mono to modern dotnet, having native linux support. Now I plan to do it, I created a simple dotnet app in Visual Studio, but what to do next, how to run it on Toolforge? Two years ago you say it should be an image, created by buildservice, too, like my old code. Could you explain how should I built a new image and run it on Toolforge? My current building scripts are here: https://github.com/Saisengen/wikibots/tree/main (you have wrote them). MBH (talk) 12:46, 1 April 2026 (UTC)

Hi @MBH! I'm a bit busy right now. You can create the new code in a new repository, and use Help:Toolforge/My first .NET tool to build + deploy it, when building, you can also give the image a different name, like <code>toolforge build start --image-name my-new-web https://gitlab.wikimedia.org/toolforge-repos/sample-dotnet-buildpack-app.git</code>. I can try to give it a look eventually, but I can't commit to anything soon. DCaro (WMF) (talk) 15:27, 1 April 2026 (UTC)

Thanks. I created a repo (https://github.com/Saisengen/webservice/tree/master) and successfully built it, now I have one more issue. When I got 500 server error on Toolforge (when debugging locally on my PC, there is no this issue), error message doesn't written into error.log file on Toolforge filesystem, unlike early behavior. Where could I read error messages? MBH (talk) 11:15, 3 April 2026 (UTC)

You can try <code>toolforge we service logs</code> (note that if the logs are older than 1h, you'll have to pass <code>--since 5h</code> for example) DCaro (WMF) (talk) 15:07, 3 April 2026 (UTC)

tools.mbh@tools-bastion-15:~$ toolforge we service logs
Usage: toolforge [OPTIONS] COMMAND [ARGS]...
Try 'toolforge --help' for help.
Error: No such command 'we'. MBH (talk) 04:32, 4 April 2026 (UTC)

that was a typo xd, it's "webservice" not "we service" DCaro (WMF) (talk) 15:09, 4 April 2026 (UTC)

And how to clean up these logs (it's useful after code refactoring, to view only new errors, not fixed old errors). MBH (talk) 14:30, 18 April 2026 (UTC)

Thanks. One more question: when I need to read a static file from Toolforge filesystem, I read it by absolute path (/data/project/mbh/file.txt) and it works. But when I want to read a file, included into build (https://github.com/Saisengen/webservice/blob/master/cpf.html for example) and try to read it by relative path (just StringReader("cpf.html")), it doesn't work. How to read files from my project? MBH (talk) 08:08, 6 April 2026 (UTC)

Your repository is cloned under /workspace, so that would be /workspace/webservice/cpf.html. Note that for you project data directory, it's better to use $TOOLFORGE_DATA_DIR instead of the absolute path, like $TOOLFORGE_DATA_DIR/file.txt in your example (see Help:Toolforge/Building container images#Using NFS shared storage). DCaro (WMF) (talk) 17:03, 7 April 2026 (UTC)

Thanks. One more question: how to log my tools usage into access.log file? MBH (talk) 15:54, 12 April 2026 (UTC)