chore: move node to /usr/libexec

[elibosley]

Summary by CodeRabbit

• Chores

  • Updated the Node.js runtime configuration for consistent execution.

• Refactor

  • Centralized the Node.js binary path into a configurable parameter for improved maintainability.

• New Features

  • Introduced a new entity declaration for NODE_DIR to streamline Node.js binary management in the plugin.
  • Updated the Node.js interpreter path in the application configuration.

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1209701840918649

[coderabbitai]

Walkthrough

This pull request updates the Node.js interpreter path references across multiple configuration files. In both the API ecosystem configuration and the Vite configuration, the interpreter path is changed from /usr/local/node/bin/node to /usr/local/bin/node, including an update to the generated shebang line. Additionally, in the plugin file, a new XML entity NODE_DIR with the value /usr/libexec/node is introduced, and related symlink commands are updated to reference this entity. No public or exported entities were modified.

Changes

Files	Change Summary
api/ecosystem.config.json, api/vite.config.ts	Updated Node.js interpreter path from /usr/local/node/bin/node to /usr/local/bin/node (including shebang update in the Vite config).
plugin/.../dynamix.unraid.net.plg	Added XML entity NODE_DIR with value /usr/libexec/node and updated symlink commands to use NODE_DIR instead of the hardcoded path.

Possibly related PRs

• fix: OEM plugin issues #1288: The changes in the main PR, which update the Node.js interpreter path in the configuration, are related to the modifications in the retrieved PR that also involve changing the Node.js path in the banner function.
• feat: download nodejs and install on legacy OS versions #970: The changes in the main PR, which update the Node.js interpreter path in the configuration, are directly related to the modifications in the retrieved PR that also involve changes to Node.js paths and configurations in the same plugin file.
• feat: track node version in slackware #949: The changes in the main PR, which update the Node.js interpreter path in the configuration, are related to the modifications in the retrieved PR that also involve changes to the Node.js path in the plugin file, specifically the NODE_DIR variable.

Suggested reviewers

• pujitm
• mdatelle

Poem

In the realm of code, paths are redefined,
Node journeys to a new home, neatly aligned.
Configs now sing a refreshed, clear song,
Steering each command steady and strong.
Cheers to the update—our code’s set on the right track!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between 65089ee and 50374c4.

📒 Files selected for processing (1)

• api/ecosystem.config.json (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• api/ecosystem.config.json

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: Test API
• GitHub Check: Build API
• GitHub Check: Build Web App
• GitHub Check: Cloudflare Pages

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

This plugin has been deployed to Cloudflare R2 and is available for testing.
Download it at this URL:

https://preview.dl.unraid.net/unraid-api/tag/PR1345/dynamix.unraid.net.plg

[pujitm]

btw does this mean node will be on PATH by default?

[elibosley]

btw does this mean node will be on PATH by default?

Unfortunately, no, but this is the location that Tom suggested we store this binary in.