[10:42:24] Hello! I'm trying to get CI working, and I've made it all the way to uvicorn starting: [10:42:25] 2025-11-02T10:33:20Z [app-74d7f4d99c-n64t6] [job] INFO:     Uvicorn running on http://0.0.0.0:8080 [10:42:25] But I get 404 at https://glamorous-maintenance-python.toolforge.org/ [10:42:26] The codebase: https://gitlab.wikimedia.org/toolforge-repos/glamorous-maintenance-python [10:42:26] Am I supposed to also start a webservice manually? Or have I missed something else? I've used https://gitlab.wikimedia.org/toolforge-repos/sample-complex-app-backend as inspiration [11:25:12] I’m confused by https://gitlab.wikimedia.org/toolforge-repos/glamorous-maintenance-python/-/blob/main/toolforge.yaml, I thought the components service isn’t available for webservices yet [11:25:17] (as stated at https://wikitech.wikimedia.org/wiki/Help:Toolforge/Deploy_your_tool) [11:29:57] yeah, you have a running deployment but no corresponding ingress yet https://paste.toolforge.org/view/c6a7e87c [11:30:16] as far as I know, what you’re trying to do with `toolforge.yaml` isn’t possible yet (though it hopefully will be soon) [11:30:53] which instructions did you follow to create that file? [11:34:56] (what you instead need is the “build the image” and “start the webservice” steps from https://wikitech.wikimedia.org/wiki/Help:Toolforge/My_first_Python_ASGI_tool#Step_3:_Prepare_the_application_for_deployment) [11:35:34] (and probably use `--port "$PORT"` instead of `--port "8080"`) [12:21:21] Beao: I replied to you without realizing you’d left for a bit, see https://wm-bot.wmcloud.org/browser/index.php?start=11%2F02%2F2025&end=11%2F02%2F2025&display=%23wikimedia-cloud [12:25:36] Thanks! I was trying to mimic the sample code, but I'm thinking the build step is successful though, considering that everything is running. Should I remove the command to run app in toolforge.yaml and start the webservice manually instead? [12:28:39] the sample code you linked is only for a backend without a publicly reachable web service [12:29:17] I guess you could still build the image from toolforge.yaml, but you’d need to start/restart the webservice manually [12:34:33] Okay, and the webservice replaces the app job by running web in Procfile? [12:35:19] yes [12:46:35] Seems to be working, thanks! [12:47:29] \o/ [14:45:15] pip not installed on bastions? [14:46:29] No, you can create a virtual env using the python container, then use that on the bastion... though it's preferred to use a container to run jobs [14:46:47] https://wikitech.wikimedia.org/wiki/Help:Toolforge/Python there is a section on here how to do it [15:11:27] Thanks buddy. Can I call my Python (venv) scripts from within PHP code? (re @wmtelegram_bot: No, you can create a virtual env using the python container, then use that on the bastion... though it's preferred to ...) [15:16:41] !log lucaswerkmeister@tools-bastion-15 tools.wdactle deployed da00a43c7d (add flex-wrap) [15:16:44] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wdactle/SAL [15:23:59] !log multichill@tools-bastion-14 tools.heritage T407159 login issue fixed, depolyed update-monuments. Created T409000 for missing jobs [15:24:04] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.heritage/SAL [15:32:41] wm-bb: Would need some more info but tentatively yes (depending on dependencies), either via a pre-created env of by using jobs-api [20:00:10] I cannot establish connection to scholia.toolforge.org or ordia.toolforge.org from one of my computers (browsers, curl, wget). On other device with another IP I can access the websites. On the computer with the problem I can access synia.toolforge.org and other toolforge.org tools. A traceroute is:  9  * * * [20:00:10] 10  vlan1120.cloudgw1003.eqiad1.wikimediacloud.org (185.15.56.245)  113.819 ms  113.698 ms  113.852 ms [20:00:11] 11  cloudinstances2b-gw.openstack.eqiad1.wikimediacloud.org (185.15.56.238)  114.506 ms  113.762 ms  113.681 ms [20:00:11] 12  cloudinstances2b-gw.openstack.eqiad1.wikimediacloud.org (185.15.56.238)  3193.506 ms !H  3079.833 ms !H  3079.739 ms !H [20:00:12] with `sudo traceroute -p 443 185.15.56.11` [20:07:57] Scholia and Ordia are currently experience excessive crawling - more than 100 req/min. Grafana shows up to 25 req/s.