[19:57:08] how do you enable a lighttpd server on toolforge? [19:58:20] something like webservice --backend=kubernetes lighttpd start? (but it's not in the list) [19:59:26] inductiveload: on the kubernetes cluster, `webservice --backedn-kubernetes php7.3 start` would probably be what you want [19:59:38] (except without the typos) [20:00:38] the php7.3 base image is lighttpd + php and expects to serve files from $HOME/public_html. This is neraly the same thing as the lighttpd backend on the grid. [20:01:19] The difference is primarily that the grid lighttpd has access to perl and python runtimes for cgi scripts as well. [20:04:49] aha, got it, thanks :-) [20:13:56] if a library loads something from some github.io resource, is that always going to be a CSP report? [20:38:42] inductiveload: yes. github is a 3rd party site external to the movement [20:41:23] what about stuff like hitting up third-party APIs - is the right thing to do there always to proxy though a toolforge back end? [20:41:31] pretty much [20:41:44] righto, makes sense [20:42:01] just checking before I make my life harder for no reason [20:52:07] rrrr the wsimedia eslint config needs eslint >= 7, but vue-cli needs < 7 [21:12:32] inductiveload: what version of vue-cli? Toolhub is using @vue/cli==4.5.13 and eslint==7.26.0 [21:12:49] below 5.0 apparently [21:13:13] (according to a github issue) [21:13:27] it works until you do `"extends": "wikimedia/client-es6"` [21:15:12] We had some troubles with something similar in the Toolhub config. It ended up being caused by us having put too many things into devDependencies. T279471 [21:15:13] T279471: Upgrade to eslint-config-wikimedia 0.20.0 - https://phabricator.wikimedia.org/T279471 [21:21:15] is this case it is [21:21:21] eslint-plugin-json-es