What's the correct way to deploy this without installing the -dev dependencies ?

_{注意:我試圖在這里創(chuàng)建一個(gè)規(guī)范的問(wèn)答來(lái)澄清奇怪的 Composer 部署.隨意編輯這個(gè)問(wèn)題.}

推薦答案

為什么

恕我直言，現(xiàn)在 Composer 將默認(rèn)使用 --dev 標(biāo)志(在安裝 和 更新時(shí))是有充分理由的.Composer 主要在需要這種行為的場(chǎng)景中運(yùn)行:

There is IMHO a good reason why Composer will use the --dev flag by default (on install and update) nowadays. Composer is mostly run in scenario's where this is desired behavior:

基本的 Composer 工作流程如下:

The basic Composer workflow is as follows:

• 啟動(dòng)一個(gè)新項(xiàng)目:composer.phar install --dev，將json和lock文件提交給VCS.
• 其他開(kāi)發(fā)人員開(kāi)始參與該項(xiàng)目:簽出 VCS 和 composer.phar install --dev.
• 開(kāi)發(fā)者添加依賴:composer.phar require ，如果你想要require-dev中的包，添加--dev代碼>部分(并提交).
• 其他人繼續(xù):(結(jié)帳和)composer.phar install --dev.
• 開(kāi)發(fā)人員想要更新版本的依賴項(xiàng):composer.phar update --dev (并提交).
• 其他人繼續(xù):(結(jié)帳和)composer.phar install --dev.
• 項(xiàng)目已部署:composer.phar install --no-dev

• A new project is started: composer.phar install --dev, json and lock files are commited to VCS.
• Other developers start working on the project: checkout of VCS and composer.phar install --dev.
• A developer adds dependancies: composer.phar require <package>, add --dev if you want the package in the require-dev section (and commit).
• Others go along: (checkout and) composer.phar install --dev.
• A developer wants newer versions of dependencies: composer.phar update --dev <package> (and commit).
• Others go along: (checkout and) composer.phar install --dev.
• Project is deployed: composer.phar install --no-dev

如您所見(jiàn)，--dev 標(biāo)志的使用(遠(yuǎn))多于 --no-dev 標(biāo)志，尤其是當(dāng)開(kāi)發(fā)人員的數(shù)量較多時(shí)項(xiàng)目成長(zhǎng).

As you can see the --dev flag is used (far) more than the --no-dev flag, especially when the number of developers working on the project grows.

生產(chǎn)部署

在不安裝dev"的情況下部署它的正確方法是什么?依賴?

What's the correct way to deploy this without installing the "dev" dependencies?

好吧，composer.json 和 composer.lock 文件應(yīng)該提交給 VCS.不要省略 composer.lock，因?yàn)樗嘘P(guān)應(yīng)該使用的包版本的重要信息.

Well, the composer.json and composer.lock file should be committed to VCS. Don't omit composer.lock because it contains important information on package-versions that should be used.

在執(zhí)行生產(chǎn)部署時(shí)，您可以將 --no-dev 標(biāo)志傳遞給 Composer:

When performing a production deploy, you can pass the --no-dev flag to Composer:

composer.phar install --no-dev

composer.lock 文件可能包含有關(guān)開(kāi)發(fā)包的信息.這沒(méi)關(guān)系.--no-dev 標(biāo)志將確保未安裝這些開(kāi)發(fā)包.

The composer.lock file might contain information about dev-packages. This doesn't matter. The --no-dev flag will make sure those dev-packages are not installed.

當(dāng)我說(shuō)生產(chǎn)部署"時(shí)，我指的是旨在用于生產(chǎn)的部署.我不是在爭(zhēng)論 composer.phar install 是否應(yīng)該在生產(chǎn)服務(wù)器上完成，或者在可以審查事情的臨時(shí)服務(wù)器上完成.這不是這個(gè)答案的范圍.我只是指出如何在不安裝dev"的情況下composer.phar install依賴.

When I say "production deploy", I mean a deploy that's aimed at being used in production. I'm not arguing whether a composer.phar install should be done on a production server, or on a staging server where things can be reviewed. That is not the scope of this answer. I'm merely pointing out how to composer.phar install without installing "dev" dependencies.

離題

--optimize-autoloader 標(biāo)志在生產(chǎn)環(huán)境中也可能是可取的(它會(huì)生成一個(gè)類映射來(lái)加速應(yīng)用程序的自動(dòng)加載):

The --optimize-autoloader flag might also be desirable on production (it generates a class-map which will speed up autoloading in your application):

composer.phar install --no-dev --optimize-autoloader

或者在自動(dòng)部署完成后:

Or when automated deployment is done:

composer.phar install --no-ansi --no-dev --no-interaction --no-plugins --no-progress --no-scripts --optimize-autoloader

如果您的代碼庫(kù)支持它，您可以將 --optimize-autoloader 換成 --classmap-authoritative.更多信息這里

If your codebase supports it, you could swap out --optimize-autoloader for --classmap-authoritative. More info here

這篇關(guān)于使用 Composer 的開(kāi)發(fā)/生產(chǎn)切換時(shí)如何正確部署?的文章就介紹到這了，希望我們推薦的答案對(duì)大家有所幫助，也希望大家多多支持html5模板網(wǎng)！