无网络环境下Symfony 2.8升级至3.4：composer本地仓库配置咨询

Absolutely, you can pull off this upgrade without internet access—using a local Composer repository is the perfect solution. Here's a step-by-step breakdown tailored to your scenario:

1. Prep the Local Package Repository (Do This on a Machine With Internet) #

First, you need to gather all required Symfony 3.4 packages and their dependencies. Here's how to do it right:

• On an internet-connected machine, create a temporary directory and initialize a basic Composer project.
• Add the exact Symfony 3.4 requirement and run a download-only command to fetch all necessary packages:

  composer require symfony/symfony:3.4.* --no-install
  composer download --prefer-dist
  

• Alternatively, if you already have a copy of your Symfony 2.8 project, run composer update symfony/symfony:3.4.* --prefer-dist --no-dev on the internet-connected machine, then copy the entire vendor directory and Composer's cache (usually ~/.composer/cache) to your offline environment.
• For a more structured long-term solution, use Satis to build a private Composer repository that mirrors all the packages you need. This makes managing versions easier for future offline updates.

2. Update Your Offline Project's composer.json #

Modify your project's composer.json to point to your local repository and target Symfony 3.4:

• Update the require section to replace Symfony 2.8 with 3.4, and adjust other dependencies to match Symfony 3.4's compatibility rules:

  "require": {
      "symfony/symfony": "3.4.*",
      // Example adjustments:
      "twig/twig": "^1.34 || ^2.0",
      "doctrine/doctrine-bundle": "^1.6"
  }
  

• Add your local repository configuration at the top of composer.json:

  "repositories": [
      {
          "type": "path",
          "url": "/path/to/your/local/packages/folder",
          "options": {
              "symlink": false
          }
      }
      // If using Satis, replace with this block:
      // {
      //     "type": "composer",
      //     "url": "file:///path/to/your/satis/repo"
      // }
  ]
  

3. Run the Offline Upgrade #

On your offline development environment, execute these Composer commands:

• First, configure Composer to skip remote repository checks entirely:

  composer config repo.packagist false
  

• Run the upgrade command, skipping scripts temporarily to avoid runtime errors during the process:

  composer update symfony/symfony --no-dev --prefer-dist --no-scripts
  

• If you hit dependency conflicts, tweak the versions in your composer.json to align with Symfony 3.4's supported packages (refer to Symfony's 3.4 docs for compatibility details).
• Finally, refresh the autoloader and run post-upgrade scripts:

  composer dump-autoload
  composer run-script post-update-cmd
  

4. Post-Upgrade Cleanup & Testing #

Symfony 2.8 to 3.4 has several deprecations and breaking changes—don't skip these critical steps:

• Audit your project code to replace deprecated methods, classes, and patterns (e.g., controller base classes, service injection styles, route annotations).
• Clear the Symfony cache to eliminate runtime inconsistencies:

  php app/console cache:clear --env=prod
  

• Run your test suite (if available) to catch any remaining compatibility gaps.

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