tar xf node-v14.16.1-linux-圆4.tar.gzĬonveniently, it creates its own directory. Of course, I chose to give it the same name as the web site file. Note that the -o option was used to give the output file the name of my choosing.
The download was accomplished with "curl". I have a "temp" directory conveniently located in my home dir. So that's what is to be downloaded using curl. Putting the two parts together, I got the following URL: In my case it was: node-v14.16.1-linux-圆4.tar.gz I wrote this down, or select-and-copied, to get the correct spelling. There I looked for the name that had "linux" and "x86" in the name. In a browser, go to download page: įind a link that says: All download optionsĬlick through that it goes to an index page with a URL like: After being frustrated when the "rpm" solutions (mentioned elsewhere) failed, I finally decided to just do the installation manually.
#INSTALL NPM UBUNTU INSTALL#
AWS encourages using nvm, node version manager, but that seems to always install in a user directory, and not a system level directory.
Surprisingly, AWS apparently doesn't give support to that idea. By that I mean install should be put in a place like /usr/bin, so that all users have access. I want a GLOBAL install of node and npm on AWS. Why mess with installers that break or don't put things where I want them? Such were the problems encountered while installing *node.js" on Amazon Web Services, that a manual install was the easy way to get the result I wanted.
0 kommentar(er)
