While the above option will let you install the required node version, it is still an approach of upgrading only the needed part of the platform (just the node package). Īfter the recipes apply, the verification of the node version installed shows: ip-10-0-3-82 ~ # node -v To do so we will need a custom chef recipe. In order to check the available versions of node/npm we can check here, since npm comes bundled with node. The package we are after is a version of net-libs/nodejs-bin because an already statically built node is the safest (in regards to dependencies) and quickest (since it will not require building) approach. In this case we are going to utilise the portage in order to add an ebuild that will install a statically built node package. Installing node versions that do not exist in portage For example, in a stable-v4-2.0.129 instance the command eix net-libs/nodejs will output: net-libs/nodejs The tool to check which versions exist is eix. There, you can find and install the desired package. The available versions of packages exist in the EY Gentoo portage tree. In this article we will outline the available options regarding nodejs. While this version could be enough for some applications, a more up to date nodejs version is sometimes required. On the stable-v4 EY stack the default version of nodejs installed is net-libs/nodejs-0.10.38. Note: The stack referred to in this article is no longer maintained and this article is kept purely for reference.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |