Replies: 4 comments
-
NPM can fail if it's missing resources. Try to increase RAM/CPU. Otherwise, maybe there has been a breaking change in a recent PingVin release. Would need to investigate |
Beta Was this translation helpful? Give feedback.
-
i have increase RAM and CPU....same error |
Beta Was this translation helpful? Give feedback.
-
also run into trouble on update
|
Beta Was this translation helpful? Give feedback.
-
managed to do the update like this cd /opt/pingvin-share pm2 stop pingvin-share-backend pingvin-share-frontend cd backend cd ../frontend |
Beta Was this translation helpful? Give feedback.
-
hello
i ve got an failed update with the script
`✓ Stopped Pingvin Share
-remote: Enumerating objects: 56, done.
remote: Counting objects: 100% (56/56), done.
remote: Compressing objects: 100% (47/47), done.
remote: Total 56 (delta 28), reused 20 (delta 9), pack-reused 0 (from 0)
Unpacking objects: 100% (56/56), 52.50 KiB | 1.94 MiB/s, done.
From https://github.com/stonith404/pingvin-share
ab4f19e..77eef18 main -> origin/main
[ERROR] in line 68: exit code 0: while executing command npm run build &> /dev/null`
Beta Was this translation helpful? Give feedback.
All reactions