Installation

Upgrade to 2.19: node problems

Re: Upgrade to 2.19: node problems

by Alexei Kolesnikov -
Number of replies: 3
Thank you, Glen! Yes, I tried that solution from the link first: roughly the same result, but with an additional warning that the ability to communicate over http has been deprecated in 2021. So the command I tried is essentially in the same spirit, but trying to use https.

Same results without 'sudo'.
In reply to Alexei Kolesnikov

Re: Upgrade to 2.19: node problems

by Glenn Rice -
Yes, not using "sudo" won't fix your issue. My point was just that you should not be using "sudo" for this in any scenario.

The stack exchange post that I linked was quite old. Here is something newer: https://medium.com/@d_dhana/working-with-npm-behind-network-proxy-444ced82a3

Unfortunately, I can't really help you with this other than to point you to things I find on the internet. I don't have a proxy requiring authentication to work behind and test this.

You could try cloning the webwork2 and pg repositories on a computer that is not behind a proxy, then run "npm ci" there (you only need to have node and npm installed on that computer for this to work), and then copy all of the htdocs directories to your server.
In reply to Glenn Rice

Re: Upgrade to 2.19: node problems

by Alexei Kolesnikov -
Update: cloning webwork2 and pg on a computer not behind the proxy, running "npm ci" and then copying over (and changing permissions) worked! I used instructions from https://webwork.maa.org/wiki/Installation_Manual_for_2.19_on_Ubuntu#Set_File_and_Directory_Permissions

I opened a service request with our tech unit to figure out how to make it work long-term; will update when there are any outcomes. Thank you again!
In reply to Alexei Kolesnikov

Re: Upgrade to 2.19: node problems

by Alexei Kolesnikov -
Update:
deb.nodesource.com was added by the technology team as an allowed domain for the proxy server. The following command now succeeds:
$ npm --proxy http://[proxy server name]:80 ci