Very much needed. To be Honest I have a legacy project that is vey critical and running on Node 10.2. We started it in 2018 on LaravelForge. One of the reasons for not migrating it to Ploi yet is that I am too lazy to install Old node version manually.

Ow yeah! This would be nice to have!

@Dennis

FYI, for now I install nvm on behalf of the user of the website and in the deploy script I put: . ~/.nvm/nvm.sh && nvm use 16

@Jurgen Indeed, this is fine and will probably also work with the installation with Ploi.

Via the manage tab, you may now install NVM or N (up to you), we're still checking of we can expand functionality.

@Dennis I've tried using this feature today by first installing nvm on the server over the manage tab and then just using the command nvm use auto in my deploy script. This outputs ploi.sh: line 8: nvm: command not found

Can you tell me/us how to correctly use this feature?

@Dennis just revisiting this. I've also didn't find nvm on the server anywhere. Is this correctly working?

I'm having the same issue. There seems to be no NVM after installing it through Ploi.

@Dennis could you please take a look? It's sad to see this issue still open. Shouldn't be that difficult to make NVM available to all system users one would think. Thanks in advance

@Jurgen Without some weird quirky workarounds it actually is pretty difficult :(

looks like nvm gets installed in the home dir of the root user

/root/.nvm

For the time being you can install it per system user.

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.4/install.sh | bash

See https://github.com/nvm-sh/nvm.

There are multiple issues to solve here, for example:

• using nvm on other users then Ploi
• pm2 is still run on "system node"
• What about globally installed npm packages.

I think i have a dirty workaround for the first issue that requires some, keep in mind this is not production ready, use at your own risk.

Install nvm via the ploi user

mkdir /usr/local/nvm
curl https://raw.githubusercontent.com/nvm-sh/nvm/master/install.sh | NVM_DIR=/usr/local/nvm bash

The dirty path

that should be changed with group privileges for example but did not get this to work yet. This makes it so every user can install and use nvm cache.

mkdir /usr/local/nvm/.cache && chmod -R 777 /usr/local/nvm/.cache
mkdir /usr/local/nvm/versions && chmod -R 777 /usr/local/nvm/versions
mkdir /usr/local/nvm/alias && chmod -R 777 /usr/local/nvm/alias

Add nvm init to profiles

echo 'export NVM_DIR="/usr/local/nvm"' | sudo tee -a /etc/profile.d/nvm.sh
echo '[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" | sudo tee -a /etc/profile.d/nvm.sh

This seems to still not be working as expected.

@Dennis Should it perhaps be moved to In progress again?

So I installed NVM via Ploi but even the default ploi user doens't have access to ploi in terminal, I get Command 'nvm' not found error (Ubuntu 22 on Hetzner)

According to https://stackoverflow.com/questions/11542846/nvm-node-js-recommended-install-for-all-users#comment58129097_19040346

... you should NOT EVER install nvm as root. nvm is per-user. If you want to share node across users, nvm is the wrong tool to use.

Please does anyone have a solution to this now ?