[00:19:15] Huh, TIL there is a deployment-prep SAL separately from the releng SAL. [00:20:54] yeah. AFAIK it's not used much (and I'm not aware of any "intentional" usage of it as distinct from the releng one, it just exists and occasionally stuff ends up in it) [00:23:20] And we still have zero.wikipedia in Beta DNS :D [00:23:47] anyway, I'll resist the urge to delete anything right now. today, we're adding :) [00:28:47] * Krinkle pretends it is not at all annoying that after every create, Horizon redirects away from the list view to the generic overview tab. [00:59:07] I think I like public suffix solution, haven't read summary yet. [00:59:21] do we sync new wiki creation in prod to a new wiki in beta? [00:59:28] of course it's very rare [01:01:15] or actually maybe I don't have a good handle on incubator graduation rate but certainly sister creation is rare [01:21:24] No, beta has a small set of mostly-fixed wikis. While specific tests scenarios to call for creation of new beta wikis from time to time (always matching a prod wiki, to maintain it as subset), wikis are not created in beta "first", or otherwise paired when creating prod wikis. [01:21:40] specific test scenarios do call* [01:24:32] I didn't mean beta first, I just meant to catch up for additions. does beta cover every alphabet? every font? [01:27:20] in terms of default logged-out content language, probably not. [01:27:30] but when you're logged in, all languages are availalbe from all wikis. [01:27:56] and there's patchdemo as well to create ad-hoc test wikis in any language as-needed. [01:28:42] project/language combos for which there are volunteers/staff who would make use of it to test there, those exist. [01:28:50] so it's lazily-created as-needed. [01:29:58] and more specifically the subset where that person/community feels beta specifically is an environment where they'd want to test . As opposed to e.g. testwiki, or patchdemo, or something else. [06:30:25] *📢 Reminder:* [06:30:26] Hi everyone! 🌿 [06:30:27] The Medic Tree Mapping Campaign orientation session* starts in 2 hours!* [06:30:29] Make sure your devices are charged and join us on time for some exciting tree mapping & wiki contributions 🌳💻 [06:30:30] See you soon! 🌍✨ *Join here: *https://meet.google.com/mka-bhsr-wqh [16:50:11] !log codesearch resizing instance sourcebot1 from g4.cores4.ram8.disk20 to g4.cores4.ram16.disk20 [16:50:13] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Codesearch/SAL [16:52:29] how is this on topic? please use https://t.me/WikimediaAnnouncements instead (re @Archies_03: 📢 Reminder: [16:52:30] Hi everyone! 🌿 [16:52:32] The Medic Tree Mapping Campaign orientation session starts in 2 hours! [16:52:33] Make sure your devices are cha...) [21:36:23] Good evening, i'm currently using a friend macbook pro to deploy a web app using nodejs but it's my first time using toolforge, please any guidance cos the documentation is overwhelming [21:43:17] There are several guides but this is a good one to start from [21:43:18] https://wikitech.wikimedia.org/wiki/Help:Toolforge/Building_container_images/My_first_static_tool_using_Node.js (re @serious: Good evening, i'm currently using a friend macbook pro to deploy a web app using nodejs but it's my first time using toolforge, ...) [21:43:28] @serious: I was going to recommend https://wikitech.wikimedia.org/wiki/Help:Toolforge/Building_container_images/My_first_static_tool_using_Node.js, but that tutorial seems to be buggy. :/ [21:46:27] bd808: It's the most recent one but I have to admit I didn't test it from start to end [21:46:39] do we need laptop:~$ part here? : https://tools-static.wmflabs.org/bridgebot/b163d21e/file_71014.jpg [21:46:53] I want to convert these boxes to syntaxhighlight (with copy button) [21:48:03] dhinus: I references a git repo that doesn't exist and then later points to one that does exist but has nothing to do with node, so yeah a bit buggy. [21:49:04] good catch thanks, I can try fixing it tomorrow if you're not faster than me :) [21:50:59] @nerim4n: I personally think the context hint about when you are local and when you are on a bastion are more helpful in those instructions than making things be button clicks for copy-and-paste, but I'm sure that is a bit subjective. [21:53:38] @serious: I think the written content in the https://wikitech.wikimedia.org/wiki/Help:Toolforge/Building_container_images/My_first_static_tool_using_Node.js is reasonably true, it is just missing a completed git demo to refer to. Basically adding a Procfile that runs `npm start` and setting up your package.json to have a `start` script are the important parts. Your nodejs webserver should listen on port 8000 as well which is not clear in that [21:53:38] tutorial. [22:12:00] actually I've finished building my project and pushed to my repo in github and when i went for the tutorial i was able to create an ssh client with openssh on the command line, and logged in alright but then i got stacked after using become toolname [22:13:19] How are you stuck? What are you hoping to do next? [22:13:42] i'm hoping to deploy next [22:15:07] ok. can you share your tool name and the git repo that you want to deploy? I can try to figure out what your next steps are from there. [22:16:55] is it okay, since this is a public platform [22:18:18] why not? you can't use this service if you're not sharing your code [22:24:37] !log tools running /srv/tools/cleanup.sh on tools-nfs-2 in a screen session, trying to clear disk space alert [22:24:40] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [22:32:33] alright the tool name is ghanasupremecases and the repo is https://github.com/Sunkanmi1/SCC-WEBAPP.git [23:10:25] `toolforge build start https://github.com/Sunkanmi1/SCC-WEBAPP` will try to build a container for the app. I don't remember if the nodejs buildpack will assume `npm start` for the web command without a Procfile, but you can try it. Once the container builds `webservice --mount=none buildservice start` would try to run it. [23:11:54] You may need to do `toolforge envars create PORT 8000` to tell your server.js what port to use. I can't remember if that port envvar is set by default in the buildpack beckend. [23:13:00] Having the node_modules directory vendored into your git repo is not a standard thing to do on our platform. [23:15:32] The use of cloudflare CDNJS mirrors is not considered a best practice in Toolforge. We would suggest using https://tools-static.wmflabs.org/cdnjs/ instead. https://wikitech.wikimedia.org/wiki/Help:Toolforge/Web#Load_external_assets_using_our_CDN_services