Merge pull request #206 from rocky-linux/develop

Release: Merge develop to main

Author: NebraskaCoder

.claude/agents/fullstack-ts-engineer.md

@@ -0,0 +1,53 @@
+---
+name: fullstack-ts-engineer
+description: Use this agent when you need expert assistance with TypeScript/JavaScript development tasks including writing new code, reviewing existing code, implementing best practices, or solving full-stack engineering challenges. This agent excels at both frontend and backend development, can search for current best practices, and provides thorough code reviews. Examples:\n\n<example>\nContext: User needs help implementing a React component with TypeScript.\nuser: "I need to create a reusable Button component with proper TypeScript types"\nassistant: "I'll use the fullstack-ts-engineer agent to help create a well-typed, reusable Button component following React best practices."\n<commentary>\nSince this involves TypeScript/React development, the fullstack-ts-engineer agent is perfect for providing expert guidance on component architecture and type definitions.\n</commentary>\n</example>\n\n<example>\nContext: User has written an Express.js API endpoint and wants it reviewed.\nuser: "I just finished writing an authentication endpoint, can you check if it follows security best practices?"\nassistant: "Let me use the fullstack-ts-engineer agent to review your authentication endpoint for security best practices and code quality."\n<commentary>\nThe user needs a code review focusing on security best practices for a backend endpoint, which is within the fullstack-ts-engineer's expertise.\n</commentary>\n</example>\n\n<example>\nContext: User needs guidance on modern JavaScript patterns.\nuser: "What's the best way to handle async operations in a Node.js application?"\nassistant: "I'll consult the fullstack-ts-engineer agent to provide expert guidance on modern async patterns in Node.js."\n<commentary>\nThis requires deep knowledge of JavaScript async patterns and best practices, making it ideal for the fullstack-ts-engineer agent.\n</commentary>\n</example>
+color: green
+---
+
+You are an expert TypeScript/JavaScript full-stack engineer with deep knowledge of the React.js library, Next.js framework, and modern development practices. You have extensive experience with TypeScript's type system, JavaScript ES6+ features (including the latest features, knowing what is available in most browsers), and the entire web development ecosystem.
+
+Your core competencies include:
+
+- Writing clean, maintainable, and performant TypeScript/JavaScript code
+- Implementing design patterns and architectural best practices
+- Conducting thorough code reviews with constructive feedback
+- Staying current with evolving best practices through research when needed
+- Understanding both browser and Node.js environments deeply
+- Database design and integration (SQL and NoSQL)
+- API design (REST, GraphQL)
+- Testing strategies (unit, integration, e2e)
+- Performance optimization techniques
+- Security best practices
+
+When assisting with code:
+
+1. **Write with clarity**: Produce code that is self-documenting with meaningful variable names and appropriate comments for complex logic
+2. **Prioritize type safety**: Leverage TypeScript's type system fully, avoiding 'any' types and ensuring proper type coverage
+3. **Follow established patterns**: Adhere to project conventions when evident, or recommend industry-standard patterns when starting fresh
+4. **Consider edge cases**: Anticipate potential issues and handle errors gracefully
+5. **Optimize thoughtfully**: Balance performance with readability, optimizing only where it provides meaningful benefit
+
+When reviewing code:
+
+1. **Identify critical issues first**: Security vulnerabilities, logic errors, or performance bottlenecks
+2. **Suggest improvements constructively**: Explain why changes would be beneficial with concrete examples
+3. **Acknowledge good practices**: Highlight what's done well to reinforce positive patterns
+4. **Consider context**: Understand the broader system and requirements before suggesting major refactors
+5. **Provide actionable feedback**: Include code snippets or specific implementation suggestions
+
+When researching best practices:
+
+1. **Search for current information**: When uncertain or when practices may have evolved, search online for the latest recommendations
+2. **Evaluate sources critically**: Prioritize official documentation, reputable blogs, and well-maintained repositories
+3. **Consider trade-offs**: Present multiple approaches when applicable, explaining pros and cons
+4. **Adapt to project needs**: Tailor general best practices to the specific context and constraints
+
+Your approach should be:
+
+- **Pragmatic**: Focus on solutions that work in real-world scenarios
+- **Educational**: Explain your reasoning to help others learn
+- **Collaborative**: Engage in technical discussions as a peer, not a lecturer
+- **Detail-oriented**: Catch subtle issues while maintaining sight of the bigger picture
+- **Proactive**: Anticipate follow-up questions and address potential concerns
+
+When you need clarification, ask specific questions about requirements, constraints, or preferences. Always strive to provide value whether writing new code, reviewing existing implementations, or sharing architectural guidance.

.claude/settings.json

@@ -0,0 +1,6 @@
+{
+  "permissions": {
+    "allow": ["Bash(git add:*)"],
+    "deny": []
+  }
+}

.devcontainer/devcontainer.json

@@ -0,0 +1,70 @@
+# GitHub Actions Workflows
+
+This directory contains GitHub Actions workflows for the Rocky Linux website.
+
+## Workflows
+
+### check-download-urls.yml
+
+This workflow automatically checks all URLs in the `data/downloads.json` file to ensure they are accessible.
+
+#### When it runs:
+
+- **On push/PR**: When `data/downloads.json` is modified
+- **Daily**: At 2 AM UTC (scheduled check)
+- **Manual**: Can be triggered manually from the Actions tab
+
+#### What it does:
+
+1. Extracts all URLs from the nested JSON structure
+2. Checks each URL using HTTP HEAD requests
+3. Reports any URLs that return errors or non-success status codes
+4. Creates issues or PR comments when failures are detected
+
+#### Local testing:
+
+You can test the URL checker locally using the standalone script:
+
+```bash
+# Run the URL checker
+node scripts/check-download-urls.js
+
+# Or make it executable and run directly
+chmod +x scripts/check-download-urls.js
+./scripts/check-download-urls.js
+```
+
+#### Features:
+
+- **Batch processing**: Checks URLs in batches to avoid overwhelming servers
+- **Progress indicator**: Shows real-time progress when run locally
+- **Detailed reporting**: Shows the JSON path and error details for each failed URL
+- **GitHub integration**: Automatically comments on PRs and creates issues for scheduled runs
+- **Smart notifications**:
+  - Updates existing PR comments instead of creating duplicates
+  - Updates existing issues instead of creating new ones daily
+  - Automatically closes issues when all URLs are fixed
+- **Prevents spam**: Only one issue and one PR comment per problem
+
+#### Expected behavior:
+
+- URLs returning 2xx or 3xx status codes are considered successful
+- 4xx or 5xx status codes are reported as failures
+- Network errors and timeouts are also reported
+- All URLs, including Docker Hub, are checked using HTTP HEAD requests. Some services (like Docker Hub) may not support HEAD requests, which can result in false negatives.
+
+### Other Workflows
+
+- **playwright.yml**: Runs Playwright end-to-end tests
+- **validate_markdown_filenames.yml**: Ensures markdown files follow naming conventions
+- **Validate.yml**: General validation workflow
+
+## Adding New Workflows
+
+When adding new workflows:
+
+1. Place the workflow file in this directory
+2. Use descriptive names ending with `.yml`
+3. Document the workflow purpose and triggers
+4. Consider adding manual trigger option (`workflow_dispatch`)
+5. Add appropriate error handling and notifications

.github/workflows/README.md

@@ -0,0 +1,173 @@
+name: Check Download URLs
+
+on:
+  push:
+    branches: [ main, develop ]
+    paths:
+      - 'data/downloads.json'
+  pull_request:
+    branches: [ main, develop ]
+    paths:
+      - 'data/downloads.json'
+  schedule:
+    # Run daily at 2 AM UTC to catch broken links
+    - cron: '0 2 * * *'
+  workflow_dispatch:
+    # Allow manual triggering
+
+jobs:
+  check-urls:
+    runs-on: ubuntu-latest
+    
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v4
+    
+    - name: Set up Node.js
+      uses: actions/setup-node@v4
+      with:
+        node-version: '20'
+    
+    - name: Extract and check URLs
+      id: url-check
+      run: node scripts/check-download-urls.js
+      env:
+        GITHUB_ACTIONS: true
+      continue-on-error: true
+    
+    - name: Comment PR on failure
+      if: steps.url-check.outcome == 'failure' && github.event_name == 'pull_request'
+      uses: actions/github-script@v7
+      with:
+        script: |
+          const fs = require('fs');
+          if (fs.existsSync('url-check-summary.md')) {
+            const summary = fs.readFileSync('url-check-summary.md', 'utf8');
+            
+            // Check for existing comments from this workflow
+            const comments = await github.rest.issues.listComments({
+              issue_number: context.issue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo
+            });
+            
+            const botComment = comments.data.find(comment => 
+              comment.user.type === 'Bot' && 
+              comment.body.includes('🚨 URL Check Failed')
+            );
+            
+            if (botComment) {
+              // Update existing comment
+              await github.rest.issues.updateComment({
+                comment_id: botComment.id,
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                body: summary + '\n\n*Updated: ' + new Date().toISOString() + '*'
+              });
+            } else {
+              // Create new comment
+              await github.rest.issues.createComment({
+                issue_number: context.issue.number,
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                body: summary
+              });
+            }
+          }
+    
+    - name: Create or update issue on scheduled run failure
+      if: steps.url-check.outcome == 'failure' && github.event_name == 'schedule'
+      uses: actions/github-script@v7
+      with:
+        script: |
+          const fs = require('fs');
+          let body = '## 🚨 Daily URL Check Failed\n\n';
+          
+          if (fs.existsSync('url-check-summary.md')) {
+            body += fs.readFileSync('url-check-summary.md', 'utf8');
+          } else {
+            body += 'The URL checker found broken links in downloads.json. Please check the workflow logs for details.';
+          }
+          
+          body += '\n\n[View latest workflow run](https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }})';
+          
+          // Check for existing open issues
+          const issues = await github.rest.issues.listForRepo({
+            owner: context.repo.owner,
+            repo: context.repo.repo,
+            state: 'open',
+            labels: 'downloads,url-check-failed'
+          });
+          
+          const existingIssue = issues.data.find(issue => 
+            issue.title === 'Broken download URLs detected'
+          );
+          
+          if (existingIssue) {
+            // Add comment to existing issue
+            await github.rest.issues.createComment({
+              issue_number: existingIssue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              body: body + '\n\n*Check performed at: ' + new Date().toISOString() + '*'
+            });
+            console.log(`Updated existing issue #${existingIssue.number}`);
+          } else {
+            // Create new issue
+            await github.rest.issues.create({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              title: 'Broken download URLs detected',
+              body: body + '\n\n*First detected: ' + new Date().toISOString() + '*\n\nThis issue will be automatically updated with new checks until resolved.',
+              labels: ['bug', 'downloads', 'url-check-failed']
+            });
+            console.log('Created new issue for broken URLs');
+          }
+    
+    - name: Close issue if URLs are fixed
+      if: steps.url-check.outcome == 'success' && github.event_name == 'schedule'
+      uses: actions/github-script@v7
+      with:
+        script: |
+          // Check for existing open issues
+          const issues = await github.rest.issues.listForRepo({
+            owner: context.repo.owner,
+            repo: context.repo.repo,
+            state: 'open',
+            labels: ['downloads', 'url-check-failed']
+          });
+          
+          const existingIssue = issues.data.find(issue => 
+            issue.title === 'Broken download URLs detected'
+          );
+          
+          if (existingIssue) {
+            // Close the issue
+            await github.rest.issues.update({
+              issue_number: existingIssue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              state: 'closed'
+            });
+            
+            // Add closing comment
+            await github.rest.issues.createComment({
+              issue_number: existingIssue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              body: '✅ All URLs are now accessible! Closing this issue.\n\n*Verified at: ' + new Date().toISOString() + '*'
+            });
+            
+            console.log(`Closed issue #${existingIssue.number} - all URLs are fixed`);
+          }
+    
+    - name: Set workflow status
+      if: always()
+      run: |
+        if [ "${{ steps.url-check.outcome }}" == "failure" ]; then
+          echo "URL check failed - marking workflow as failed"
+          exit 1
+        else
+          echo "URL check passed"
+          exit 0
+        fi