10-20-2024, 02:34 PM
(This post was last modified: 10-20-2024, 02:35 PM by JimmyKing.
Edit Reason: oops
)
I've overhauled my script.
Main differences being:
- Removed interactive elements
- Added best-guess for node based upon dependency checking
- Added optional arguments that override defaults & best-guess
Just note that relying on the default best-guess Node setup is likely to fail at some point. In such cases, you'll have to look at the release announcements and specify the required Node version as an argument with '-n <version>'. I asked on the Plex forums about extending an existing endpoint to include the Node requirements, but they obviously have their own ideas.
Not sure how useful this is for you, but feel free to use/adapt/ignore. I was hoping to find a more robust node solution...
Main differences being:
- Removed interactive elements
- Added best-guess for node based upon dependency checking
- Added optional arguments that override defaults & best-guess
Just note that relying on the default best-guess Node setup is likely to fail at some point. In such cases, you'll have to look at the release announcements and specify the required Node version as an argument with '-n <version>'. I asked on the Plex forums about extending an existing endpoint to include the Node requirements, but they obviously have their own ideas.
Not sure how useful this is for you, but feel free to use/adapt/ignore. I was hoping to find a more robust node solution...
