創(chuàng)建.github/workflows/ci-cd.yml 文件以定義工作流，觸發(fā)條件為推送到或合併到main 分支，並配置MySQL 服務(wù)；2. 在測(cè)試任務(wù)中檢出代碼、設(shè)置PHP 環(huán)境、安裝依賴、生成應(yīng)用密鑰、配置.env 文件、運(yùn)行遷移並執(zhí)行phpunit 測(cè)試；3. 可選但推薦添加PHPStan 等工具進(jìn)行代碼質(zhì)量檢查；4. 使用appleboy/ssh-action 通過(guò)SSH 部署到服務(wù)器，僅在main 分支推送且測(cè)試通過(guò)後運(yùn)行，並通過(guò)GitHub Secrets 管理敏感信息；5. 所有敏感配置使用環(huán)境變量和GitHub Secrets 注入，避免硬編碼；6. 建議使用actions/cache 緩存Composer 依賴以提升性能。該流程實(shí)現(xiàn)了Laravel 應(yīng)用的自動(dòng)化測(cè)試與持續(xù)部署，確保代碼質(zhì)量並提高發(fā)布效率。

Setting up a CI/CD pipeline for a Laravel application using GitHub Actions is straightforward and powerful. It helps automate testing, linting, and deployment workflows every time you push or merge code. Here's how to do it step by step.

? 1. Create the GitHub Actions Workflow File

Start by creating a .github/workflows/ci-cd.yml file in your Laravel project. This defines your CI/CD pipeline.

 name: Laravel CI/CD

on:
  push:
    branches: [ main ]
  pull_request:
    branches: [ main ]

jobs:
  test:
    runs-on: ubuntu-latest

    services:
      mysql:
        image: mysql:8.0
        env:
          MYSQL_ROOT_PASSWORD: rootpassword
          MYSQL_DATABASE: homestead
          MYSQL_USER: homestead
          MYSQL_PASSWORD: secret
        ports:
          - 3306:3306
        options: --health-start-period=20s --health-interval=10s

This configures the workflow to run on every push or PR to main , and sets up a MySQL service for testing.

? 2. Set Up the Environment and Run Tests

Inside the test job, install dependencies and run Laravel's test suite.

 steps:
      - name: Checkout code
        uses: actions/checkout@v4

      - name: Setup PHP
        uses: shivammathur/setup-php@v2
        with:
          php-version: '8.2'
          extensions: mbstring, dom, pdo, sqlite, pdo_sqlite, mysql, zip
          coverage: none

      - name: Validate composer.json and composer.lock
        run: composer validate --strict

      - name: Install dependencies
        run: composer install -q --no-ansi --no-interaction --no-scripts --no-progress

      - name: Generate application key
        run: php artisan key:generate

      - name: Create Laravel .env file
        run: cp .env.example .env

      - name: Run Laravel migrations
        run: php artisan migrate --database=mysql --force
        env:
          DB_CONNECTION: mysql
          DB_HOST: 127.0.0.1
          DB_PORT: 3306
          DB_DATABASE: homestead
          DB_USERNAME: homestead
          DB_PASSWORD: secret

      - name: Execute tests (phpunit)
        run: vendor/bin/phpunit

? This ensures your Laravel app boots up, connects to the database, migrates, and runs unit/feature tests.

? 3. Add Code Linting (Optional but Recommended)

You can include PHP_CodeSniffer or PHPStan for code quality checks.

 - name: Install dev dependencies
        run: composer install -q

      - name: Run PHPStan
        run: vendor/bin/phpstan analyse app --level=7

Make sure phpstan/phpstan is in require-dev .

? 4. Set Up Deployment (CD) via SSH or Deployers

For continuous deployment (eg, to a VPS), you can use tools like appleboy/ssh-action .

?? Store credentials in GitHub Secrets ( DEPLOY_HOST , DEPLOY_USER , SSH_PRIVATE_KEY , etc.)

 deploy:
    needs: test
    runs-on: ubuntu-latest
    if: github.ref == 'refs/heads/main' && github.event_name == 'push'

    steps:
      - name: Deploy to production server
        uses: appleboy/ssh-action@v1.0.1
        with:
          host: ${{ secrets.DEPLOY_HOST }}
          username: ${{ secrets.DEPLOY_USER }}
          key: ${{ secrets.SSH_PRIVATE_KEY }}
          script: |
            cd /var/www/your-laravel-app
            git pull origin main
            composer install --no-dev --optimize-autoloader
            php artisan migrate --force
            php artisan config:cache
            php artisan route:cache
            php artisan view:cache
            sudo systemctl reload nginx

This step only runs on pushes to main after tests pass.

? 5. Environment Variables & Secrets

Never hardcode credentials. Use:

• .env.example for template
• GitHub Secrets for sensitive values in workflows

In your workflow, inject secrets as environment variables where needed.

? Summary of Key Points

• ? Use ubuntu-latest runner with PHP and MySQL services
• ? Run composer install , migrate , and phpunit
• ? Keep deployment separate and conditional
• ? Use GitHub Secrets for SSH keys and DB credentials
• ? Cache dependencies (optional for speed):

 - name: Cache Composer packages
        uses: actions/cache@v3
        with:
          path: vendor
          key: composer-${{ hashFiles('composer.lock') }}

That's it. Your Laravel app now has automated testing on every change and automatic deployment to production when code lands on main . It's not magic — just consistent, reliable automation.

以上是如何使用github動(dòng)作為L(zhǎng)aravel設(shè)置CI/CD管道？的詳細(xì)內(nèi)容。更多資訊請(qǐng)關(guān)注PHP中文網(wǎng)其他相關(guān)文章！