feat: Add lablink-update command for easy code updates #90
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.
Adds a comprehensive update system to ensure Docker containers always reflect the latest code changes after git pull.
New features:
lablink-update command (installed on all new Pi images):
Standalone script (lablink-update.sh):
Updated helper commands and documentation:
Usage:
On Pi with new image:
sudo lablink-update
On existing Pi:
cd /opt/lablink
curl -O https://raw.githubusercontent.com/X9X0/LabLink/main/lablink-update.sh
chmod +x lablink-update.sh
sudo ./lablink-update.sh
This solves the problem where git pull updates files but Docker containers continue running old code until manually rebuilt.