docs(exedev): remove misleading journalctl monitoring command#231
Open
andrerfneves wants to merge 1 commit into
Open
docs(exedev): remove misleading journalctl monitoring command#231andrerfneves wants to merge 1 commit into
andrerfneves wants to merge 1 commit into
Conversation
The Monitoring section listed a journalctl command for a systemd service that is never set up in the deployment guide. The guide only covers PM2 and Docker for process management. The misleading command would produce 'Unit lightning-decoder.service not found' for anyone following the guide.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Removes a misleading
journalctl -u lightning-decodercommand from the Monitoring section ofDEPLOYMENT_EXEDEV.md.Why
The guide covers PM2 and Docker for process management, neither of which sets up a systemd unit named
lightning-decoder. Thejournalctl -u lightning-decodercommand would produceUnit lightning-decoder.service not foundfor anyone following the guide.Changes
DEPLOYMENT_EXEDEV.md: Removed the# System logs/journalctl -u lightning-decoderlines from the View Logs section. PM2 and Docker log commands remain.Test Plan