[05:08:37] !log tools.github-pr-closer Restarting web service to make it canonical [05:08:39] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.github-pr-closer/SAL [10:58:52] !log toolsbeta run `aborrero@toolsbeta-puppetdb-02:~ $ sudo systemctl restart puppetdb` the service was in failed state, causing puppet failures across the whole project [10:58:54] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Toolsbeta/SAL [11:05:12] !log toolsbeta poweroff `toolsbeta-services-01`. I suspect this VM is not in use because no puppet role is in used there [11:05:14] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Toolsbeta/SAL [11:59:18] !log tools `root@tools-sge-services-03:~# aptly db cleanup` removed 340 unreferenced packages, and 2 unreferenced files [11:59:21] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [12:03:01] Hello, is it passible to make changes to nginx default.conf for my tool on Toolforge? [12:05:41] iridescence: hi there, what would you like to acomplish? [12:06:36] !log tools uploaded tools-webservice v0.68 to stretch-toolsbeta for testing [12:06:38] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [12:06:52] !log toolsbeta installing tools-webservice v0.68 for testing [12:06:53] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Toolsbeta/SAL [12:07:00] Something like: location / { [12:07:01] try_files $uri $uri/ /index.html; [12:07:01] } [12:07:19] but for only my tool page [12:08:00] you want index.html to be your default file? [12:08:41] Yeah, something like that to get use of react-router [12:18:06] is that possible on Toolforge? [12:20:03] iridescence: I'm not familiar with react-router. Depending on the backend you are using, there are some options you can change on your server (be it nginx, lighttpd, uwsgi, etc) [12:20:56] I'm multitasking right now, give me a few minutes so I can focus here and do proper search on wikitech [12:21:02] It's kind of a static site [12:21:24] Yeah, it's no hurry. Take your time :) [12:21:44] BTW did you search in wikitech already? [12:22:06] if there is no info there, perhaps sending an email to cloud@l.w.o and see if some other person already has the same use case [12:22:19] or open a phab task with a feature request, that's also a valid approach :-) [12:22:27] but if you wait a bit I will investigate myself [12:22:38] I can wait [12:46:14] !log tools uploading tools-webservice v0.68 to aptly stretch-tools and update it on relevant servers (T250625) [12:46:17] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [12:46:17] T250625: tools.wmflabs.org to Toolforge.org redirect query / post string propagation - https://phabricator.wikimedia.org/T250625 [13:28:11] !log tools shutdown elasticsearch v5 cluster running Jessie T236606 [13:28:14] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [13:28:14] T236606: Rebuild Toolforge elasticsearch cluster with Stretch or Buster - https://phabricator.wikimedia.org/T236606 [14:04:33] arturo: How long is a bit? :) [14:04:49] iridescence: sorry I'm now in a meeting :-/ [14:17:24] ping joakino [14:43:53] iridescence: the nginx services in Toolforge are only reverse proxies and not content serving webservers. The PHP webservice types have a lighttpd webserver that the tool maintainer can configure. There is some documentation on that at https://wikitech.wikimedia.org/wiki/Help:Toolforge/Web/Lighttpd [14:45:08] The node types do not have any webserver process in the container. [14:47:41] bd808: So is it passible to do something like this ngnix configuration in lighttpd: https://pastebin.com/ywLC92em ? [14:47:52] !log tools added joakino to tools.admin LDAP group [14:47:54] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [14:47:58] !log toolsbeta added joakino to toolsbeta.admin LDAP group [14:47:59] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Toolsbeta/SAL [14:51:53] Or is there a way to run a docker container? [14:53:00] iridescence: url.rewrite-if-not-file is a bit like nginx's try_files -- https://redmine.lighttpd.net/projects/lighttpd/wiki/Docs_ModRewrite#urlrewrite-repeat-if-not-file [14:53:26] iridescence: No, Toolforge does not support "bring your own container" at this time. And honestly we are unlikely to ever support fully custom container not built on our base images. [14:54:58] We are doing some very early experimental work towards build pack configured images, but that is not likely to be usable for most tools for many more months [14:58:54] i'm not familiar with lighttpd, but I will try. [15:31:01] !log tools Rebuilding Docker containers to pick up tools-webservice v0.68 (T250625) [15:31:05] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [15:31:05] T250625: tools.wmflabs.org to Toolforge.org redirect query / post string propagation - https://phabricator.wikimedia.org/T250625 [15:41:20] !log deployment-prep Deploying ORES 5d977f4 [15:41:22] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Deployment-prep/SAL [15:56:20] bd808: I can't manage it to work, and I do not fully understand Lighttpd. [16:10:37] iridescence: maybe we should back up so I can understand what you are hoping to accomplish. The XY problem happens a lot to folks in Toolforge where they have a solution in mind from another platform but Toolforge's stack is different enough that we end up talking past each other. [16:10:59] https://en.wikipedia.org/wiki/XY_problem [16:11:58] iridescence: having your tool name might help too. I can use my admin powers to look at things directly [16:21:40] bd808: Okay, here we go. I spent hole Easter making an application in “create-react-app”. The application has no backend, client only. The purpose of the tool is to import Spotify albums to Wikidata. So there is use of Spotifys’ API to create the pages. In other words, the pages are dynamic. I do have a dockerfile that creates a working environment, if that is of any help. Now I want to deploy the app. on Toolforge for [16:21:40] others to use it. The biggest problem so far is the dynamic pages does not work. I use “react-router” for dynamic creations. The tool is named: moedata. [16:22:42] iridescence: ah. that's the tool I saw stuck in crashloopbackoff over the weekend :) [16:23:58] Oh, sorry. Where should we start? :) [16:26:50] iridescence: so does "react-router" expect that any URL is actually mapped back to the a particular HTML document? Similar to how something like a PHP application with a single entrypoint php script works? [16:29:56] iridescence: I guess what I am really asking is if you know which URL patterns need to be matched to which on disk assets? [16:31:39] Well, with nginx I used this. And it worked: https://pastebin.com/ywLC92em [16:32:12] `try_files $uri $uri/ /index.html;` is a lot of nginx magic :) [16:33:01] that basically says: look for the file on disk, if not found look for a directory on disk, if not found then return index.html [16:34:57] Hmmm... not sure if there is any other way to do it [16:37:00] When I load https://tools.wmflabs.org/moedata/ in my browser it logs a bunch of js syntax errors, which I think would be unrelated to the webserver routing [16:37:24] * bd808 looks around some more in the deployed tool [16:44:30] iridescence: ok. I see your $HOME/.lighttpd.conf file. This is telling lighttpd to return $HOME/public_html/index.html for all requests. That is pretty certainly not what you actually want (and the cause of the js errors in my console) [16:45:28] Yeah, I have tried a lot of different config. but none of them work as intended. [16:47:50] I have tried to explain the usage here, if it is to any help :) https://github.com/DiFronzo/MoeData [16:54:43] iridescence: I think that makes some sense. As I'm understanding this the tool is using the /album/.... URLs to provide deep linking ability into the client side js. This is similar to a more old school /#!... routing [16:55:17] iridescence: do all of your deep links start with /album/ ? [16:55:47] I have another for /artist/ but that is not finished, yet. [16:56:31] iridescence: *nod* I think the lighttpd config should only try rewriting these prefixes then [16:57:41] iridescence: to do that you would change `"(.*)"` to something like `"((/moedata)?/artist/.*)" in your rewrite rule [16:57:50] the [16:58:37] But should it redirect to index.html or something else? [16:59:11] the "(/moedata)?" part is so that the tool name prefix is optional. That can be dropped if you start using --canonical and force all interactions to https://moedata.toolforge.org/ [17:00:29] iridescence: I think it would go to your index, yes. The URL for that depends on if the visitor is using https://tools.wmflabs.org/moedata/ or https://moedata.toolforge.org/ which is another reason to make it all simpler with --canonical. See https://wikitech.wikimedia.org/wiki/News/Toolforge.org [17:06:55] bd808: Looks like all my static files also get "overwritten" with this rule :( [17:53:26] Hi, is it right https://tools.wmflabs.org/ipcheck?ip=62.148.157.220 doesn't redirect to http://ipcheck.toolforge.org/?ip=62.148.157.220? [17:57:06] Urbanecm: its a bug. We actually just rolled out a potential fix today. [17:57:27] thanks bd808! [18:27:45] iridescence: sorry, I got into the meeting heavy section of my work day. I will try to think about your problem a bit more in ~2 hours. I think its going to be possible, just a bit annoying to get it working right. :) [18:28:22] iridescence: maybe you could start a Phabricator task where we can keep track of the problem and the things we have tried to solve it? [18:28:22] Nice :) [18:29:40] sure [18:52:26] !log deployment-prep Deploying ORES a5a5bce [18:52:30] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Deployment-prep/SAL [19:16:06] !log deployment-prep Deploying ORES ac2eb2f [19:16:09] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Deployment-prep/SAL [19:47:58] !log deployment-prep Deploying ORES 514f94a [19:48:01] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Deployment-prep/SAL [21:06:13] If I understand https://replag.toolforge.org/ correctly, the wikicommons database replica is 8h behind the production database? [21:07:09] don-vip: that looks to be the case right now, yes [21:07:47] is it always so high, or a temporary problem? [21:08:30] a lag that large is often a sign that some heavy updates are happening on the production slice right now. I'd have to go look at phabricator and the server admin logs (SAL) to see why. [21:08:57] ok, thank you [21:09:07] don-vip: not "normal" but also generally not something to raise alarms about. The DBA team tracks this stuff pretty closely. [21:09:58] really large lags can catch up quickly when the source or destination is unblocked [21:10:15] ok. I was just surprised to not see a file I uploaded 2 hours ago [21:11:51] we get spoiled by the modern system. :) Over the weekend some of us were chatting in another channel about the typical lag for the replicas in the toolserver.org days (pre-2014). It wasn't too weird then for the lag to be 7 days all of the time. [21:13:05] haha [21:13:48] we often forget how amazing is the WMF infra, and don't realize all the magic happening behind the scene :) [21:14:45] pain is relative and humans are better at remembering bad things than good things :) [21:15:30] yep, good things are invisible and taken for granted [21:37:26] iridescence: I think that https://tools.wmflabs.org/moedata/ may be getting closer to working. Check out what I did in the $HOME/.lighttpd.conf file and let me know if you have questions [21:39:22] iridescence: We can make this config a little less complex if you switch to only allowing https://moedata.toolforge.org/ URLs. See https://wikitech.wikimedia.org/wiki/News/Toolforge.org for info on that [21:40:24] * bd808 disappears into another block of meetings [21:40:50] Do you have meeting now? [21:41:00] meetings* [21:41:10] iridescence: unfortunately, yes [21:41:44] I should be done around 23:00 UTC (~1:20 from now) [21:41:52] Oh, okay. Should I still create that phabricator task? [21:42:01] iridescence: sure! [23:52:14] I will let you know when I see iridescence and I will deliver that message to them [23:52:14] @notify iridescence It's alive! https://moedata.toolforge.org/album/2ABAeQdTwWlZZj4cW2zOWX