You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When rosetta is ready to be upgraded to node 18 on phet-server-dev, the systemd file /usr/lib/systemd/system/rosetta.service should point to /home/phet-admin/.nvm/versions/node/v18.16.0/bin/npm instead of /usr/local/bin/npm.
EDIT: if you wait a while to do this, the minor and/or maintenance versions of node may have changed, please check the target before hard coding 18.16.0 using which node in an interactive shell for phet-admin. Note: sudo -u phet-admin which node will report the node version for your user, not phet-admin. It's required that phet-admin's .bashrc has been loaded in the current shell, for example you could run sudo -i -u phet-admin then which node.
The text was updated successfully, but these errors were encountered:
I tried changing the rosetta.service file today on phet-server2, and it didn't work. After changing the path to npm like MP suggested above, I ran sudo systemctl daemon-reload, then sudo systemctl restart rosetta. When I did, it failed. I am not sure why.
A few notes for posterity:
The rosetta.service file wasn't in /usr/lib/systemd/system/. It was in /etc/systemd/system/.
The rosetta.service file uses /home/phet-admin/.nvm/versions/node/v16.14.2/bin/npm. It does not use /usr/local/bin/npm.
When changing the Node version, you also have to change the Environment key so that it has the correct npm in its PATH.
@mattpen, Rosetta is running on Node 18 using my Mac computer. I haven't seen any issues. @jbphet also is able to run Rosetta + Node 18 on Windows, so we are pretty confident it is ready once phet-server2 has Node 18 installed.
When rosetta is ready to be upgraded to node 18 on phet-server-dev, the systemd file
/usr/lib/systemd/system/rosetta.service
should point to/home/phet-admin/.nvm/versions/node/v18.16.0/bin/npm
instead of/usr/local/bin/npm
.This should be done before node 16 end of life on 09-11-2023 - https://github.com/nodejs/release#release-schedule
EDIT: if you wait a while to do this, the minor and/or maintenance versions of node may have changed, please check the target before hard coding 18.16.0 using
which node
in an interactive shell for phet-admin. Note:sudo -u phet-admin which node
will report the node version for your user, not phet-admin. It's required that phet-admin's .bashrc has been loaded in the current shell, for example you could runsudo -i -u phet-admin
thenwhich node
.The text was updated successfully, but these errors were encountered: