{ "id": 74, "uuid": "dca13bd4-9c2d-4bfd-85b2-4db8d6a99b5f", "share_token": "9MUZaq4Ws9TR", "title": "PHP 项目部署方式", "plain_text": "You:\nphp web项目，当前线上代码更新用的还是FTP文件替换的方式更新代码，如果不上容器，有别的更好的方式吗？\n\n---\n\nChatGPT:\n可以。不上容器，也比 FTP 覆盖文件强很多。推荐按成熟度分三档：\n\n方案 1：Git 拉代码部署，最低改造\n\n适合：小团队、单机 PHP 项目、暂时不想引入复杂 CI\/CD。\n\n流程\n\n服务器上保留项目 Git 仓库：\n\nBash\ncd \/var\/www\/project\ngit fetch origin\ngit checkout main\ngit pull\ncomposer install --no-dev --optimize-autoloader\nphp artisan migrate --force # Laravel 才需要\nphp artisan config:cache # Laravel 才需要\nsudo systemctl reload php-fpm\n优点\n\n比 FTP 安全、可追踪\n\n能知道线上当前是什么 commit\n\n可以快速回滚：\n\nBash\ngit checkout \ncomposer install --no-dev --optimize-autoloader\nsudo systemctl reload php-fpm\n问题\n\n部署过程中可能出现“半更新”状态\n\n多台机器同步麻烦\n\n权限、缓存、依赖安装容易出问题\n\n适合作为第一步替代 FTP，但不是最终形态。\n\n方案 2：CI\/CD 自动部署，推荐起点\n\n适合：希望团队规范化，不想手动登录服务器。\n\n可以用：\n\nGitHub Actions\n\nGitLab CI\n\nJenkins\n\nGitea Actions\n\nCoding \/ 阿里云云效 \/ 腾讯 CODING\n\n基本逻辑\n\n开发合并到 main 或打 tag 后自动执行：\n\n拉代码\n\n安装依赖\n\n跑测试\n\n打包产物\n\n上传到服务器\n\n执行部署脚本\n\nreload PHP-FPM \/ Nginx\n\n例如用 GitHub Actions + SSH：\n\nYAML\nname: Deploy\n\non:\n push:\n branches: [main]\n\njobs:\n deploy:\n runs-on: ubuntu-latest\n\n steps:\n - uses: actions\/checkout@v4\n\n - name: Install dependencies\n run: composer install --no-dev --optimize-autoloader\n\n - name: Deploy via SSH\n uses: appleboy\/ssh-action@v1.0.3\n with:\n host: ${{ secrets.SERVER_HOST }}\n username: ${{ secrets.SERVER_USER }}\n key: ${{ secrets.SERVER_KEY }}\n script: |\n cd \/var\/www\/project\n git pull origin main\n composer install --no-dev --optimize-autoloader\n sudo systemctl reload php-fpm\n优点\n\n不再人工 FTP\n\n有部署日志\n\n权限可控\n\n可以加测试、审批、通知\n\n适合团队协作\n\n问题\n\n如果只是 git pull 覆盖线上目录，仍然存在短暂不一致风险。\n\n方案 3：Release 目录 + 软链接切换，强烈推荐\n\n这是不上容器时比较稳的 PHP 部署方式。\n\n目录结构\nBash\n\/var\/www\/project\/\n releases\/\n 20260615120000\/\n 20260615123000\/\n shared\/\n .env\n storage\/\n uploads\/\n current -> \/var\/www\/project\/releases\/20260615123000\n\nNginx 指向：\n\nNginx\nroot \/var\/www\/project\/current\/public;\n部署流程\n\n每次发布新建一个 release 目录：\n\nBash\nRELEASE=\/var\/www\/project\/releases\/$(date +%Y%m%d%H%M%S)\n\ngit clone git@github.com:xxx\/project.git $RELEASE\ncd $RELEASE\n\ncomposer install --no-dev --optimize-autoloader\n\nln -s \/var\/www\/project\/shared\/.env $RELEASE\/.env\nln -s \/var\/www\/project\/shared\/storage $RELEASE\/storage\n\nln -sfn $RELEASE \/var\/www\/project\/current\n\nsudo systemctl reload php-fpm\n回滚\n\n只需要把 current 指回上一个 release：\n\nBash\nln -sfn \/var\/www\/project\/releases\/20260615120000 \/var\/www\/project\/current\nsudo systemctl reload php-fpm\n优点\n\n发布接近原子切换\n\n回滚很快\n\n不会出现 FTP 那种文件传一半线上就混乱的问题\n\n很适合 PHP-FPM + Nginx 架构\n\n这个是我最推荐的非容器方案。\n\n可以直接用的工具\n\n如果不想自己写部署脚本，可以看这些：\n\n工具\t适合场景\nDeployer\tPHP 项目非常适合，支持 release、shared、rollback\nCapistrano\tRuby 生态老牌部署工具，也可部署 PHP\nAnsible\t多服务器、配置管理、发布流程统一\nJenkins\/GitLab CI\t公司内部规范 CI\/CD\nGitHub Actions\t轻量、成本低、上手快\n\n其中 Deployer 很适合 PHP：\n\nBash\ncomposer require deployer\/deployer --dev\nvendor\/bin\/dep init\nvendor\/bin\/dep deploy production\n\n它天然支持：\n\nreleases\n\nshared files\n\nsymlink\n\nrollback\n\ncomposer install\n\ndeploy hooks\n\n我的建议\n\n你们现在是 FTP 替换，建议按这个路线走：\n\n第一阶段：马上替换 FTP\n\n用：\n\nGit + SSH 部署脚本\n\n目标是先解决：\n\n文件不可追踪\n\n人工替换容易漏文件\n\n无部署日志\n\n回滚困难\n\n第二阶段：标准化发布\n\n升级成：\n\nCI\/CD + releases 目录 + current 软链接\n\n这是不上容器时的主力方案。\n\n第三阶段：补齐工程规范\n\n增加：\n\nGit 分支策略：dev \/ staging \/ main\n\n测试环境自动部署\n\n线上发布需要 tag 或手动审批\n\n部署前自动备份\n\n数据库 migration 谨慎执行\n\n发布失败自动回滚\n\n发布通知到 Slack \/ 飞书 \/ 企业微信\n\n注意几个坑\n1. 不要把用户上传文件放在代码目录里\n\n比如：\n\nBash\npublic\/uploads\nstorage\nruntime\n\n这些应该放到 shared，然后软链接进 release。\n\n否则每次发版可能覆盖或丢失用户文件。\n\n2. .env 不进 Git\n\n线上配置应该在服务器的 shared\/.env。\n\n代码发布时软链接进去。\n\n3. Composer 不建议在线上临时慢慢装\n\n更稳的方式是 CI 阶段装好依赖、打包上传。\n\n如果项目不大，也可以先在线上执行：\n\nBash\ncomposer install --no-dev --optimize-autoloader\n\n但要注意 composer 版本、PHP 扩展、网络稳定性。\n\n4. 数据库变更要单独谨慎处理\n\n代码回滚容易，数据库回滚不一定容易。\n\n建议：\n\nmigration 向前兼容\n\n大字段变更提前做\n\n删除字段延后\n\n关键发布前备份数据库\n\n结论\n\n不上容器，最推荐：\n\nGitLab CI \/ GitHub Actions + SSH + Deployer \/ Release 软链接部署\n\n这是比 FTP 稳定很多、成本又不高的方案。\n\n如果你们当前技术债不重，可以直接上 Deployer；如果团队想完全可控，就自己写 release 部署脚本。", "sanitized_html": "

You<\/div>

php web项目，当前线上代码更新用的还是FTP文件替换的方式更新代码，如果不上容器，有别的更好的方式吗？<\/div><\/div>\n

ChatGPT<\/div>

可以。不上容器，也比 FTP 覆盖文件强很多。推荐按成熟度分三档：<\/p>\n

方案 1：Git 拉代码部署，最低改造<\/h2>\n
适合：小团队、单机 PHP 项目、暂时不想引入复杂 CI\/CD。<\/p>\n

流程<\/h3>\n

服务器上保留项目 Git 仓库：<\/p>\n

<\/pre>Bash<\/div><\/div><\/div>cd<\/span> \/var\/www\/project<\/span>
git<\/span> fetch origin<\/span>
git<\/span> checkout main<\/span>
git<\/span> pull<\/span>
composer install <\/span>--no-dev<\/span>--optimize-autoloader<\/span>
php artisan migrate <\/span>--force<\/span># Laravel 才需要<\/span>
php artisan config:cache       <\/span># Laravel 才需要<\/span>
sudo<\/span> systemctl reload php-fpm<\/span><\/code><\/pre><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>\n优点<\/h3>\n\n\n比 FTP 安全、可追踪<\/p>\n<\/li>\n
\n能知道线上当前是什么 commit<\/p>\n<\/li>\n
\n可以快速回滚：<\/p>\n<\/li>\n<\/ul>\n
<\/pre>Bash<\/div><\/div><\/div>git<\/span> checkout <previous_commit><\/span>
composer install <\/span>--no-dev<\/span>--optimize-autoloader<\/span>
sudo<\/span> systemctl reload php-fpm<\/span><\/code><\/pre><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>\n问题<\/h3>\n\n\n部署过程中可能出现“半更新”状态<\/p>\n<\/li>\n
\n多台机器同步麻烦<\/p>\n<\/li>\n
\n权限、缓存、依赖安装容易出问题<\/p>\n<\/li>\n<\/ul>\n
适合作为第一步替代 FTP，但不是最终形态。<\/p>\n
\n方案 2：CI\/CD 自动部署，推荐起点<\/h2>\n适合：希望团队规范化，不想手动登录服务器。<\/p>\n
可以用：<\/p>\n
\n\nGitHub Actions<\/p>\n<\/li>\n
\nGitLab CI<\/p>\n<\/li>\n
\nJenkins<\/p>\n<\/li>\n
\nGitea Actions<\/p>\n<\/li>\n
\nCoding \/ 阿里云云效 \/ 腾讯 CODING<\/p>\n<\/li>\n<\/ul>\n
基本逻辑<\/h3>\n开发合并到 main<\/code> 或打 tag 后自动执行：<\/p>\n
\n\n拉代码<\/p>\n<\/li>\n
\n安装依赖<\/p>\n<\/li>\n
\n跑测试<\/p>\n<\/li>\n
\n打包产物<\/p>\n<\/li>\n
\n上传到服务器<\/p>\n<\/li>\n
\n执行部署脚本<\/p>\n<\/li>\n
\nreload PHP-FPM \/ Nginx<\/p>\n<\/li>\n<\/ol>\n
例如用 GitHub Actions + SSH：<\/p>\n
<\/pre>YAML<\/div><\/div><\/div>name: Deploy<\/span>

on:<\/span>
  push:<\/span>
    branches: [main]<\/span>

jobs:<\/span>
  deploy:<\/span>
    runs-on: ubuntu-latest<\/span>

    steps:<\/span>
      - uses: actions\/checkout@v4<\/span>

      - name: Install dependencies<\/span>
        run: composer install --no-dev --optimize-autoloader<\/span>

      - name: Deploy via SSH<\/span>
        uses: appleboy\/ssh-action@v1.0.3<\/span>
        with:<\/span>
          host: ${{ secrets.SERVER_HOST }}<\/span>
          username: ${{ secrets.SERVER_USER }}<\/span>
          key: ${{ secrets.SERVER_KEY }}<\/span>
          script: <\/span>|<\/span>
            cd \/var\/www\/project<\/span>
            git pull origin main<\/span>
            composer install --no-dev --optimize-autoloader<\/span>
            sudo systemctl reload php-fpm<\/span><\/code><\/pre><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>\n优点<\/h3>\n\n\n不再人工 FTP<\/p>\n<\/li>\n
\n有部署日志<\/p>\n<\/li>\n
\n权限可控<\/p>\n<\/li>\n
\n可以加测试、审批、通知<\/p>\n<\/li>\n
\n适合团队协作<\/p>\n<\/li>\n<\/ul>\n
问题<\/h3>\n如果只是 git pull<\/code> 覆盖线上目录，仍然存在短暂不一致风险。<\/p>\n
\n方案 3：Release 目录 + 软链接切换，强烈推荐<\/h2>\n这是不上容器时比较稳的 PHP 部署方式。<\/p>\n
目录结构<\/h3>\n<\/pre>Bash<\/div><\/div><\/div>\/var\/www\/project\/<\/span>
  releases\/<\/span>
20260615120000<\/span>\/<\/span>
20260615123000<\/span>\/<\/span>
  shared\/<\/span>
    .env<\/span>
    storage\/<\/span>
    uploads\/<\/span>
  current <\/span>-<\/span>> \/var\/www\/project\/releases\/20260615123000<\/span><\/code><\/pre><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>\nNginx 指向：<\/p>\n
<\/pre>Nginx<\/div><\/div><\/div>root \/var\/www\/project\/current\/public;<\/span><\/code><\/pre><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>\n部署流程<\/h3>\n每次发布新建一个 release 目录：<\/p>\n
<\/pre>Bash<\/div><\/div><\/div>RELEASE<\/span>=<\/span>\/var\/www\/project\/releases\/$(date +%Y%m%d%H%M%S)<\/span>

git<\/span> clone <\/span>git<\/span>@github.com:xxx\/project.git <\/span>$RELEASE<\/span>
cd<\/span>$RELEASE<\/span>

composer install <\/span>--no-dev<\/span>--optimize-autoloader<\/span>

ln<\/span>-s<\/span> \/var\/www\/project\/shared\/.env <\/span>$RELEASE<\/span>\/.env<\/span>
ln<\/span>-s<\/span> \/var\/www\/project\/shared\/storage <\/span>$RELEASE<\/span>\/storage<\/span>

ln<\/span>-sfn<\/span>$RELEASE<\/span> \/var\/www\/project\/current<\/span>

sudo<\/span> systemctl reload php-fpm<\/span><\/code><\/pre><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>\n回滚<\/h3>\n只需要把 current<\/code> 指回上一个 release：<\/p>\n
<\/pre>Bash<\/div><\/div><\/div>ln<\/span>-sfn<\/span> \/var\/www\/project\/releases\/20260615120000 \/var\/www\/project\/current<\/span>
sudo<\/span> systemctl reload php-fpm<\/span><\/code><\/pre><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>\n优点<\/h3>\n\n\n发布接近原子切换<\/p>\n<\/li>\n
\n回滚很快<\/p>\n<\/li>\n
\n不会出现 FTP 那种文件传一半线上就混乱的问题<\/p>\n<\/li>\n
\n很适合 PHP-FPM + Nginx 架构<\/p>\n<\/li>\n<\/ul>\n
这个是我最推荐的非容器方案。<\/p>\n
\n可以直接用的工具<\/h2>\n如果不想自己写部署脚本，可以看这些：<\/p>\n
工具<\/th> 适合场景<\/th><\/tr><\/thead>
Deployer<\/strong><\/td> PHP 项目非常适合，支持 release、shared、rollback<\/td><\/tr>
Capistrano<\/strong><\/td> Ruby 生态老牌部署工具，也可部署 PHP<\/td><\/tr>
Ansible<\/strong><\/td> 多服务器、配置管理、发布流程统一<\/td><\/tr>
Jenkins\/GitLab CI<\/strong><\/td> 公司内部规范 CI\/CD<\/td><\/tr>
GitHub Actions<\/strong><\/td> 轻量、成本低、上手快<\/td><\/tr><\/tbody><\/table><\/div><\/div>\n其中 Deployer<\/strong> 很适合 PHP：<\/p>\n
<\/pre>Bash<\/div><\/div><\/div>composer require deployer\/deployer <\/span>--dev<\/span>
vendor\/bin\/dep init<\/span>
vendor\/bin\/dep deploy production<\/span><\/code><\/pre><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>\n它天然支持：<\/p>\n
\n\nreleases<\/p>\n<\/li>\n
\nshared files<\/p>\n<\/li>\n
\nsymlink<\/p>\n<\/li>\n
\nrollback<\/p>\n<\/li>\n
\ncomposer install<\/p>\n<\/li>\n
\ndeploy hooks<\/p>\n<\/li>\n<\/ul>\n
\n我的建议<\/h2>\n你们现在是 FTP 替换，建议按这个路线走：<\/p>\n
第一阶段：马上替换 FTP<\/h3>\n用：<\/p>\n
Git + SSH 部署脚本<\/strong><\/p>\n
目标是先解决：<\/p>\n
\n\n文件不可追踪<\/p>\n<\/li>\n
\n人工替换容易漏文件<\/p>\n<\/li>\n
\n无部署日志<\/p>\n<\/li>\n
\n回滚困难<\/p>\n<\/li>\n<\/ul>\n
第二阶段：标准化发布<\/h3>\n升级成：<\/p>\n
CI\/CD + releases 目录 + current 软链接<\/strong><\/p>\n
这是不上容器时的主力方案。<\/p>\n
第三阶段：补齐工程规范<\/h3>\n增加：<\/p>\n
\n\nGit 分支策略：dev \/ staging \/ main<\/code><\/p>\n<\/li>\n
\n测试环境自动部署<\/p>\n<\/li>\n
\n线上发布需要 tag 或手动审批<\/p>\n<\/li>\n
\n部署前自动备份<\/p>\n<\/li>\n
\n数据库 migration 谨慎执行<\/p>\n<\/li>\n
\n发布失败自动回滚<\/p>\n<\/li>\n
\n发布通知到 Slack \/ 飞书 \/ 企业微信<\/p>\n<\/li>\n<\/ul>\n
\n注意几个坑<\/h2>\n
1. 不要把用户上传文件放在代码目录里<\/h3>\n比如：<\/p>\n
<\/pre>Bash<\/div><\/div><\/div>public\/uploads<\/span>
storage<\/span>
runtime<\/span><\/code><\/pre><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>\n这些应该放到 shared<\/code>，然后软链接进 release。<\/p>\n
否则每次发版可能覆盖或丢失用户文件。<\/p>\n
\n2. .env<\/code> 不进 Git<\/span><\/h3>\n线上配置应该在服务器的 shared\/.env<\/code>。<\/p>\n
代码发布时软链接进去。<\/p>\n
\n3. Composer 不建议在线上临时慢慢装<\/h3>\n更稳的方式是 CI 阶段装好依赖、打包上传。<\/p>\n
如果项目不大，也可以先在线上执行：<\/p>\n
<\/pre>Bash<\/div><\/div><\/div>composer install <\/span>--no-dev<\/span>--optimize-autoloader<\/span><\/code><\/pre><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>\n但要注意 composer 版本、PHP 扩展、网络稳定性。<\/p>\n
\n4. 数据库变更要单独谨慎处理<\/h3>\n代码回滚容易，数据库回滚不一定容易。<\/p>\n
建议：<\/p>\n
\n\nmigration 向前兼容<\/p>\n<\/li>\n
\n大字段变更提前做<\/p>\n<\/li>\n
\n删除字段延后<\/p>\n<\/li>\n
\n关键发布前备份数据库<\/p>\n<\/li>\n<\/ul>\n
\n结论<\/h2>\n不上容器，最推荐：<\/p>\n
\nGitLab CI \/ GitHub Actions + SSH + Deployer \/ Release 软链接部署<\/strong><\/p>\n<\/blockquote>\n
这是比 FTP 稳定很多、成本又不高的方案。<\/p>\n
如果你们当前技术债不重，可以直接上 Deployer<\/strong>；如果团队想完全可控，就自己写 release 部署脚本。<\/p><\/div><\/div><\/div>",
    "markdown_content": null,
    "source_platform": "ChatGPT",
    "source_url": "https:\/\/chatgpt.com\/c\/6a2f5683-2a04-8330-bf53-4a7b996820d6",
    "model_name": null,
    "metadata": {
        "tags": [
            "chatgpt",
            "ai-conversation"
        ],
        "locale": "zh_CN",
        "language": "en-US",
        "exported_at": "2026-06-15T01:35:28.540Z",
        "message_count": 2,
        "plugin_version": "1.0.0",
        "conversation_id": "6a2f5683-2a04-8330-bf53-4a7b996820d6",
        "user_message_count": 1,
        "submission_token_type": "user",
        "assistant_message_count": 1
    },
    "views_count": 30,
    "unique_views_count": 14,
    "created_at": "2026-06-15T01:35:31+00:00",
    "url": "https:\/\/chat-view.com\/s\/9MUZaq4Ws9TR"
}