Upgrade from 4.3 to 4.4 fails (behind proxy)

[m4z]

As mentioned in #56, I had huge problems with upgrading Rocket.Chat from 4.3 to 4.4 because some of the npm packages used seemed to ignore or incorrectly use the proxy, https-proxy and ca-file settings from .npmrc, which is why I had to manually point them to the https-proxy and the ca-file when they seemed to ignore the ca-file and wanted to use the (http) proxy for https sites.

I don't know much about node, the npm package "meteor" (or npm or node trying to do something with meteor) threw some vacuous error that I don't have anymore because we don't retain the logs that long. Here's what I had to do, emulating what rocketchatctl wanted to do:

curl -L https://releases.rocket.chat/4.4.0/download -o /tmp/rocket.chat.tgz
tar -xzf /tmp/rocket.chat.tgz -C /tmp
cd /tmp/bundle/programs/server && npm install --verbose
# threw an error
cd node_modules/fibers   # or maybe it was npm/node_modules/fibers/
http_proxy=http://proxy.mydomain.example:3129 '/usr/local/bin/node' '/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js' 'rebuild' '--release' --verbose --cafile=/etc/ssl/certs/cacert.pem
find . -iname binding.gyp
cd -
http_proxy=http://proxy.mydomain.example:3129 npm install --verbose
mv /tmp/bundle /opt/Rocket.Chat/
chown -R rocketchat:rocketchat /opt/Rocket.Chat/
systemctl restart rocketchat.service

I hope this is at least somewhat useful. 😞