https://wiki.linuxsa.org/index.php?action=history&feed=atom&title=Composer
Composer - 版本历史
2026-04-19T09:07:26Z
本wiki上该页面的版本历史
MediaWiki 1.43.1
https://wiki.linuxsa.org/index.php?title=Composer&diff=249&oldid=prev
Evan：/* Composer2修改源 */
2023-09-22T08:32:16Z
<p><span class="autocomment">Composer2修改源</span></p>
<p><b>新页面</b></p><div>=Composer2修改源=<br />
<pre><br />
<br />
wget https://getcomposer.org/download/latest-2.2.x/composer.phar<br />
sudo mv composer.phar /usr/sbin/composer<br />
放到 /usr/sbin 再给 777吧 测试的 <br />
<br />
a). 配置只在当前项目生效<br />
<br />
composer config repo.packagist composer https://mirrors.aliyun.com/composer/<br />
<br />
# 取消当前项目配置<br />
composer config --unset repos.packagist<br />
<br />
b). 配置全局生效<br />
<br />
composer config -g repo.packagist composer https://mirrors.aliyun.com/composer/<br />
<br />
# 取消全局配置<br />
composer config -g --unset repos.packagist<br />
<br />
<br />
<br />
/usr/sbin/composer.phar config repo.packagist composer https://mirrors.aliyun.com/composer/<br />
/opt/remi/php73/root/bin/php /usr/sbin/composer.phar update<br />
</pre><br />
<br />
=Composer修改源=<br />
composer config -g repo.packagist composer https://mirrors.cloud.tencent.com/composer<br />
<br />
[https://learnku.com/articles/15977/composer-accelerate-and-modify-mirror-source-in-china Composer 国内加速，修改镜像源 ]<br />
<br />
[https://blog.csdn.net/qq_45163122/article/details/107141435 Composer切换国内源]<br />
<br />
=laravel composer=<br />
<pre><br />
** php composer ins<br />
composer install<br />
php artisan migrate<br />
php artisan db:seed<br />
php artisan storage:link<br />
<br />
mkdir bootstrap/cache<br />
mkdir storage/framework<br />
mkdir storage/framework/cache<br />
mkdir storage/framework/views<br />
mkdir storage/framework/sessions<br />
</pre><br />
<br />
<br />
== composer install和composer update的区别==<br />
<br />
这样的结果可能是包太新哦 <br />
当你执行composer update的时候，composer会去读取composer.json中指定的依赖，去分析他们，并且去拉取符合条件最新版本的依赖。然后他会把所拉取到的依赖放入vendor目录下，并且把所有拉取的依赖的精确版本号写入composer.lock文件中。<br />
<br />
<br />
composer.json 是放在 git ?<br />
composer install所执行的事情非常类似，只在第一步的时候有差别。当你本地如果已经存在一份composer.lock时，它将会去读取你的composer.lock而非composer.json，并且以此为标准去下载依赖。当你本地没有composer.lock的时候，它所做的事情和composer update其实并没有区别。<br />
<br />
这意味着，只要你本地有一份composer.lock，你就可以保证无论过去了多久，你都能拉到相同的依赖。而如果你把它纳入你的项目的版本控制中，那么你就可以确保你项目中的每一个人、每一台电脑，不管什么系统，都能拉取到一模一样的依赖，以减少潜在的依赖对部署的影响。当然，请记得，你应该使用的命令是composer install。<br />
<br />
composer update will update your depencencies as they are specified in composer.json<br />
<br />
=see also=<br />
<br />
[https://www.runoob.com/w3cnote/composer-install-and-usage.html Composer 安装与使用]<br />
<br />
[https://developer.aliyun.com/composer 阿里云 Composer 全量镜像]<br />
<br />
[https://www.jianshu.com/p/2d260e2c5eae composer install和composer update的区别]<br />
<br />
[https://stackoverflow.com/questions/33052195/what-are-the-differences-between-composer-update-and-composer-install What are the differences between composer update and composer install]<br />
<br />
[[category:php]]</div>
Evan