Laravel部署因migrate操作失败，请求排查部署脚本故障

Hey there, let's break down why your Laravel migration is failing during deployment. First, here's the partial problematic deployment script you shared:

image: php:7-fpm
pipelines:
  branches:
    # 提交代码到分支时自动运行的流水线
    staging:
      - step:
          script:
            - apt-get update && apt-get install -y unzip python-dev git
            - apt-get install -qy git curl libmcrypt-dev mysql-client
            - docker-php-ext-install mcrypt && docker-php-ext-install pdo_mysql
            - ./install-composer.sh
            - composer install
            - export APP_ENV=QA
            - export S3_ACCESS_KEY_ID=AAAAA
            - export S3_BUCKE...

Looking at this, there are several likely culprits and fixes you can try:

1. You're not actually running the migrate command! #

The biggest red flag here is that your script cuts off before executing php artisan migrate—you set up the environment but never trigger the migration itself.

Fix: Add the migrate command (with --force to skip interactive prompts, which is critical for automated pipelines) after setting your environment variables:

- php artisan migrate --force

2. Missing database connection configuration #

You set APP_ENV=QA, but Laravel needs database credentials to connect and run migrations. Without variables like DB_HOST, DB_DATABASE, DB_USERNAME, and DB_PASSWORD, it can't reach your QA database.

Fix: Add these database exports to your script:

- export DB_HOST=your-qa-db-host
- export DB_PORT=3306
- export DB_DATABASE=qa_laravel_db
- export DB_USERNAME=qa_db_user
- export DB_PASSWORD=qa_db_password

3. Database user permissions issues #

Even if you have the right credentials, the database user might not have the necessary permissions to create/alter tables (which migrations require).

Fix:

• Verify your QA database user has CREATE, ALTER, DROP, and INSERT permissions on the target database.
• Add a quick connectivity test to your script to catch this early:

- mysql -h $DB_HOST -u $DB_USERNAME -p$DB_PASSWORD -e "SELECT 1;" $DB_DATABASE

If this command fails, you know the problem is with database access, not the migration itself.

4. Incomplete environment setup #

Depending on your Laravel version, you might need to generate an application key or ensure the .env file is properly configured. If your project relies on a .env file instead of raw environment variables:

Fix: Add these steps after composer install:

- cp .env.example .env
- php artisan key:generate

5. Truncated S3 configuration #

Your script cuts off at S3_BUCKE...—while this might not directly break migrations, if any of your migration logic interacts with S3 (e.g., storing assets), incomplete S3 credentials could cause errors.

Fix: Complete the S3 environment variables:

- export S3_SECRET_ACCESS_KEY=your-s3-secret-key
- export S3_BUCKET=your-qa-s3-bucket
- export S3_REGION=your-s3-region

Start with adding the migrate command first—That's the most obvious missing piece. If that still fails, work through the other checks one by one.

内容的提问来源于stack exchange，提问作者thitami