[03:15:24] <wm-bot>	 !log bsadowski1@tools-bastion-13 tools.stewardbots Restarted StewardBot/SULWatcher because of an EventStreams issue
[03:15:27] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.stewardbots/SAL
[09:37:03] <wm-bb>	 <dpriskorn> Hi :)
[09:37:04] <wm-bb>	 <dpriskorn> I rewrote a Python app that could not run in Toolforge in React recently. I would like to try to deploy it in Toolforge. See https://github.com/dpriskorn/topic-creator-frontend
[09:37:05] <wm-bb>	 <dpriskorn> I see no Tutorials_for_popular_languages in the wiki for node.js, but I found out that heruko has a buildpack https://github.com/heroku/buildpacks-nodejs
[09:37:07] <wm-bb>	 <dpriskorn> Does anyone have tips to help get me started?
[10:46:51] <dhinus>	 dpriskorn: following the instructions for that heroku buildpack should work in toolforge as well
[10:48:19] <dhinus>	 we've been meaning to add a node.js tutorial to the wiki but never got around to doing that, if you manage to deploy your app successfully and you want to add a short tutorial yourself, you're more than welcome!
[10:49:24] <dhinus>	 if you never deployed other apps in toolforge, you can follow the high-level steps from any other tutorial (python or php are probably good ones to copy from)
[12:48:01] <wm-bb>	 <dpriskorn> I'm curious if a multi-staged build would be preferable in Toolforge. ie the app is build and the static html is served using nginx, see https://www.docker.com/blog/how-to-dockerize-react-app/
[13:53:39] <andrewbogott>	 kamila_: I made some changes to the horizon login process. It doesn't fix /my/ problem but can you check and see if it fixes yours?
[13:53:48] <andrewbogott>	 Again, I'd say start in a private browser tab to make sure it's a clean test.
[13:56:23] <dhinus>	 dpriskorn: multi-stage builds for static websites are very cool, but they are not supported in toolforge at the moment. we mostly rely on upstream buildpacks from heroku, and they don't support that either.
[13:58:47] <kamila_>	 andrewbogott: same 401
[13:59:20] <andrewbogott>	 ok, thanks for checking
[13:59:36] <kamila_>	 https://www.irccloud.com/pastebin/dB1RiqQ6/
[14:01:51] <andrewbogott>	 kamila_: that's after you enter your username and password?
[14:02:17] <kamila_>	 yes
[14:40:20] <wm-bb>	 <dpriskorn> ok, I understand. I'll keep it simple then (re @wmtelegram_bot: <dhinus> dpriskorn: multi-stage builds for static websites are very cool, but they are not supported in toolforge at the moment....)
[18:28:48] <andrewbogott>	 kamila_: on the offhand chance that you are still around/awake, can you try logging into horizon again?
[18:29:40] <andrewbogott>	 and, I guess I'd appreciate a horizon login test from a couple other people if anyone is feeling charitable :)
[18:31:06] <kamila_>	 andrewbogott: works now! nice \o/
[18:31:13] <andrewbogott>	 all right!
[18:31:15] <andrewbogott>	 thank you for testing
[18:31:26] <kamila_>	 thank you for fixing :-) 
[18:31:40] <andrewbogott>	 This fix is actually a disservice to your name, since all I did was change the mapping to use ID instead of name and ID is ascii
[18:32:00] <andrewbogott>	 so your name may show up weird in the UI, no promises.
[18:32:02] <kamila_>	 :D
[18:33:40] <kamila_>	 UI has charset=utf-8, so it works there
[18:34:01] <andrewbogott>	 cool
[18:34:33] <wm-bb>	 <lucaswerkmeister> horizon is working for me too fwiw :)
[18:34:46] <andrewbogott>	 lucas, did you try logging out and in again?
[18:35:13] <wm-bb>	 <lucaswerkmeister> I first tried a normal tab but it made me log in there too (guess it’s been too long since last time), then a private window. both worked
[18:36:31] <andrewbogott>	 awesome
[18:36:35] <andrewbogott>	 thank you for testing!
[18:36:39] <wm-bb>	 <lucaswerkmeister> np ^^
[18:36:51] <andrewbogott>	 just in case, I'm leaving instructions on how to revert in T388137
[18:36:52] <stashbot>	 T388137: horizon: some users get 401 unauthorized - https://phabricator.wikimedia.org/T388137
[19:27:49] <wm-bot>	 !log lucaswerkmeister@tools-bastion-13 tools.wd-image-positions deployed b8022cddca (l10n updates: tr)
[19:27:52] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wd-image-positions/SAL
[19:28:46] <wm-bot>	 !log lucaswerkmeister@tools-bastion-13 tools.ranker deployed 5ced6327b8 (l10n updates: nl)
[19:28:47] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.ranker/SAL
[20:13:24] <wm-bb>	 <dpriskorn> I found out that this is probably not true. :) I successfully build my app using serve and it should serve a static build now on https://topic-curator.toolforge.org
[20:13:25] <wm-bb>	 <dpriskorn> See https://github.com/dpriskorn/topic-creator-frontend/blob/main/DEVELOPMENT.md for my draft tutorial. (re @wmtelegram_bot: <dhinus> dpriskorn: multi-stage builds for static websites are very cool, but they are not supported in toolforge at the moment....)
[20:19:30] <wm-bb>	 <dpriskorn> All requests are served in less than 30 ms on average from the cluster. 🎉 It's crazy fast compared to my earlier flask app with exactly the same features which had multi-second load times for some pages.