-
Notifications
You must be signed in to change notification settings - Fork 1
Add comprehensive beta testing system for remote testing #38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
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
✨ Features Added: - Automated GitHub Actions workflow for PR-based beta releases - Docker-based deployment system with one-click testing - Web interface for easy beta deployment and management - REST API endpoints for beta container management - Shareable link generation for easy distribution - Comprehensive testing documentation and guides 🛠️ Technical Implementation: - GitHub Actions workflow (.github/workflows/beta-release.yml) - Beta deployment API (app/api/beta_deployment.py) - Web deployment interface (frontend/beta-deploy.html) - Deployment scripts (scripts/deploy-beta.sh, scripts/generate-beta-link.py) - Issue templates for structured feedback collection - Complete documentation (BETA_SETUP.md, BETA_TESTING.md) 🎯 Benefits: - Zero installation required for testers - Instant access to latest changes via PR comments - Multiple testing methods (Docker, web interface, live URLs) - Automated cleanup when PRs are closed - Professional presentation with branded interface - Structured feedback collection system 🔧 Configuration: - Updated app.py to include beta deployment router - Added CORS support for beta deployment endpoints - Integrated with existing FastAPI application structure This system enables easy remote testing for US-based team members without requiring them to install dependencies or set up the development environment locally.
- Changed 'type=sha,prefix={{branch}}-' to 'type=sha,prefix=sha-'
- This prevents invalid tag format like 'ghcr.io/waldronlab/bioanalyzer:-b475833'
- The branch name was causing a hyphen at the start of the tag, which is invalid Docker format
…ensitive information Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
…as HTML Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
…as HTML Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
- Fixed merge conflict markers that were causing syntax errors - Added proper handling for multiple Docker tags (extract first tag only) - Added error handling with try-catch block for better debugging - Removed emojis to avoid potential character encoding issues - Added debug logging to help troubleshoot future issues The workflow should now run successfully without JavaScript syntax errors.
- Use JSON output from metadata action instead of multi-line tags string - Parse tags from JSON to get clean first tag without newlines - Use full image tag directly instead of constructing from registry/image - This fixes the SyntaxError caused by multi-line tag string in JavaScript The workflow should now handle Docker tags correctly without syntax errors.
Beta Release Ready for Testing!\n\nPR #38 has been automatically deployed for testing.\n\n### Test Your Changes\nLive Demo: https://bioanalyzer-beta-38.vercel.app\n\n### Docker Image\n
|
- Replaced template literals with properly escaped string concatenation - Used \n for newlines and \\ for backslashes in YAML - Removed problematic backticks and square brackets that caused syntax errors - This should resolve the SyntaxError: Invalid or unexpected token The workflow should now run successfully without JavaScript syntax errors.
- Add deployments: write permission for both jobs - Create proper GitHub deployment with deployment ID - Link deployment status to actual deployment ID instead of context.payload - Fix code formatting and indentation - Remove unnecessary comments and clean up spacing This should resolve all workflow issues and enable proper deployment tracking.
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.
Features Added:
Technical Implementation:
Benefits:
Configuration:
This system enables easy remote testing without requiring to install dependencies or set up the development environment locally.
Closes: #37