Ensure .dappnode_profile is sourced in all shell environments #670
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.
DAppNode commands were not available in some installations because the
.dappnode_profilefile was only being added to.profile, but many interactive shell sessions use.bashrcinstead.Problem
The installation script only added profile sourcing to the
.profilefile:This caused issues because:
.bashrc.profileAs a result, users would find that DAppNode commands like
dappnode_help,dappnode_status, etc. were not available in their shell sessions.Solution
Enhanced both installation and uninstallation scripts to handle both
.profileand.bashrcfiles:Installation (
scripts/dappnode_install.sh):Uninstallation (
scripts/dappnode_uninstall.sh):Benefits
.profile) and interactive shells (.bashrc)Users will now have access to all DAppNode commands in any shell environment without requiring manual configuration.
Fixes #664.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.