Rename database schema and update references#33
Merged
Conversation
…r.sh Rename the stream manager script for branding consistency with the LyreBirdAudio suite. This change updates: - Script file renamed from mediamtx-stream-manager.sh to lyrebird-stream-manager.sh - Log file path changed from /var/log/mediamtx-stream-manager.log to /var/log/lyrebird-stream-manager.log - All references across 14 files updated: - lyrebird-orchestrator.sh - lyrebird-diagnostics.sh - lyrebird-mic-check.sh - lyrebird-updater.sh - install_mediamtx.sh - config/mediamtx-audio.service - config/lyrebird-logrotate.conf - tests/test_integration.bats - tests/test_stream_manager.bats - tests/README.md - README.md - CONTRIBUTING.md - CHANGELOG.md - .github/ISSUE_TEMPLATE/bug_report.md Note: Existing installations will need to: 1. Update any systemd service files to reference the new script name 2. Rename or symlink the old log file if log history is needed 3. Update any custom scripts or cron jobs that reference the old name
Adds a migration framework to handle breaking changes during updates: lyrebird-updater.sh v1.6.0: - New run_post_update_migrations() runs after each update - migration_stream_manager_rename() handles the script rename: - Updates systemd service file references - Removes old script from /usr/local/bin - Installs new script to /usr/local/bin - Migrates log file with backward-compatible symlink - Updates cron job references - Migrations are idempotent (tracked via /var/lib/lyrebird/migrations/) - New --migrate CLI flag for manual migration runs lyrebird-orchestrator.sh: - New check_pending_migrations() runs at startup - Detects old script names in system locations - Alerts users with clear remediation steps - Non-blocking: warns but doesn't prevent operation This ensures users upgrading from older versions will automatically have their installations migrated to use the new script names.
- CHANGELOG.md: Document breaking change with migration instructions - README.md: Add Migration Notes section in Version Management Ensures users are fully informed about the script rename and know how to handle both automatic and manual migrations.
The root SECURITY.md is the GitHub security policy (vulnerability reporting, disclosure process), while docs/SECURITY-GUIDE.md is a user guide for securing deployments (TLS, authentication, etc.). Renaming clarifies their different purposes and reduces confusion.
Restructured curl|grep pattern to preserve curl exit status for better error detection during stream validation. The new pattern explicitly checks curl's exit code before parsing the response, making network failures more transparent. Changes: - Capture curl response in variable before pattern matching - Use bash string matching instead of piping to grep - Add version comment for traceability - Bump version to 1.4.4
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
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.
No description provided.