[00:01:49] HTriedman: I've been web searching for "heroku nodejs static files" and https://medium.com/simplejs/deploy-static-files-on-heroku-7e55e01a5df9 is the simplest example I've found so far. Depending on where your built view files end up you might need to do a bit more. [00:02:58] you also might need to be explict in your Procfile about the `web` target being something like `npm start` or whatever your package.json scripts entrypoint ends up being [00:04:02] * bd808 wanders off but will probably be online again in a couple of hours [07:05:03] HTriedman, bd808 using https://gitlab.wikimedia.org/toolforge-repos/sample-static-buildpack-app to get you a webservice + nodejs as specified https://gitlab.wikimedia.org/toolforge-repos/nodejs-flask-buildpack-sample (that ends up using both, node + python buildpacks) should work, I can try to come up with some sample on how to do so if you still have issues [13:59:48] Hi, I have a noob question about the Cloud VPS Instances. We have a cloud bps instance with name "imagehash" and there is virtual server named "test". Initially when we requested the instance we had two users me and Tuukka and these users were automatically created to the test servers when we created server.  Now I added a third member to the [13:59:49] project via Cloud VPS Instances web interface ( https://horizon.wikimedia.org/project/member/ ). It seems that user was not created to virtual server with name "test" automatically. [13:59:49] So I would like to confirm that it should be working so that I need to create the local user in "test" virtual server manually? [14:05:24] zache: the user access is managed dynamically through ldap, if your VM is using ldap (default), it might take a minute to sync, but they should have gained access. Note that the users are not local to the machine, so you would not see then in /etc/passwd and similar. Have they logged into the VM? [14:13:40] also fyi, the home directory will be created on the first login (if that's what you are looking at) [14:14:14] yes, that is what i was looking at. User has not tried yet to log in. [14:15:11] thanks [14:15:18] from 'id ' inside the VM, you can see which groups that user has, it should have `project-imagehash`, if they do they should be good to go [15:34:57] Some of y'all may not have noticed https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Changelog yet. Watchlisting this page can get you notices of new Toolforge features as they are added. [15:36:23] ^uooo looks pretty now [15:37:35] I'm glad you like my changes dcaro :) [17:48:51] !log lucaswerkmeister@tools-bastion-13 tools.wd-image-positions deployed 53074960ca (l10n updates: es, fr) [17:48:53] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wd-image-positions/SAL [18:26:48] bd808 just wanted to follow-up — the final link you sent last night (https://medium.com/simplejs/deploy-static-files-on-heroku-7e55e01a5df9) worked for me! just installed a newer version of the `serve` package, replaced the procfile with a very simple file called `serve.json` that points the server to serve the `dist/` directory, and was able to [18:26:49] successfully run the toolforge commands [19:39:32] HTriedman: I'm glad you got things working :) [21:32:19] * bd808 goes to see what is up with stashbot