Fix running npm package forever in chapter 4 #573
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This addresses an issue in the nodejs example of chapter 4. On some systems the path to the binary of the npm package 'forever' might not be `/usr/local/bin/forever`. Fixed by instead using `npx` to run it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change was also done in the manuscript repo geerlingguy/ansible-for-devops-manuscript#6
On some systems the path to the binary of the npm package 'forever' might not be /usr/local/bin/forever.
I am currently using a virtual machine running Debian 12.
I installed nodejs 20 with this role https://github.com/geerlingguy/ansible-role-nodejs
and forever based on the example from the book:
The examples in the book for running "forever" did not work because it seems that in my case the binary is not located at /usr/local/bin/forever.
I think this can be solved by using npx to run the command instead.
It should work on any system regardless where npm chooses to install the binary.
I verified the change in my setup and I can access the nodejs app and am seeing "Hello World!" as expected.
Happy New Year !