composer-php

Is it okay to run php artisan :clear commands on a production laravel website? [closed]

独自空忆成欢 提交于 2020-07-21 03:13:51
问题 Closed . This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post. Closed 2 months ago . Improve this question I have a production Laravel website hosted on a DigitalOcean NGINX server, and every time I git push new updates, I always run the following commands: php artisan config:clear php artisan cache:clear php artisan route:clear php artisan view:clear

Composer, Laravel and local packages

最后都变了- 提交于 2020-07-17 06:47:20
问题 My issue is I have a package which isn't a repository and I am trying to get it to play nice with Laravel and composer. It is still located under the vendor folder, the only issue is that if I simply set: "psr-0": { "Test\\Test": "vendor/test/test/src/" } This will load the service provider but none of the controllers etc will autoload. What is the correct way to implement a package with larval that does not have it's own repository. Or does this go against the nature of packages and this

Installing only single package via Composer without updating other packages

送分小仙女□ 提交于 2020-07-15 15:10:06
问题 I need to install a single composer package into a project - maatwebsite/excel ~2.1.0 . Each time composer updates, it updates all packages in composer.json. How can I avoid updating packages aside from the excel library? I have tried the following commands but they don't seem to be working: composer require maatwebsite/excel ~2.1.0 composer require vendor/maatwebsite/excel ~2.1.0 composer update maatwebsite/excel ~2.1.0 composer update vendor/maatwebsite/excel ~2.1.0 I've also tried using

Composer can't install Twig Extensions

萝らか妹 提交于 2020-07-09 05:57:08
问题 I tried installing the twig/extensions package in it's dev-master version in my Symfony 5 application. I am meeting the following output : Your requirements could not be resolved to an installable set of packages. Problem 1 - Installation request for twig/extensions dev-master -> satisfiable by twig/extensions[dev-master]. - Conclusion: remove twig/twig v3.0.3 - Conclusion: don't install twig/twig v3.0.3 - twig/extensions dev-master requires twig/twig ^2.10 -> satisfiable by twig/twig[v2.10.0

Call to undefined function GuzzleHttp\Psr7\get_message_body_summary()

走远了吗. 提交于 2020-06-29 07:05:26
问题 I am trying to perform CURL get request in guzzlehttp to check if a user exists in a CRM. Whenever I try to perform the request I get the following error in the title, I haven't been able to find any resources online for this specific problem. Any ideas would be super helpful, if you require any additional info please let me know in the comments. Included packages: require(__DIR__ . "/../../vendor/autoload.php"); require_once(__DIR__ . "/../../helpers/Validation.php"); use Symfony\Component

Should a package major version change mean a sub-package major version change?

北城以北 提交于 2020-06-28 03:28:10
问题 Let's say I have a core CMS which has been upgraded from v4.8.7 to v5.0.0 I also have an events module package with it's own version number 1.2.4 which imports this core CMS package in it's composer.json file: "company-name/cms": "^4.3", I upgrade the composer.json file on this package to become: "company-name/cms": "^5.0", But how do I mark this change with semantic versioning? Should it be marked as a breaking change and thus mean the submodule version number would become 2.0.0 or should it

Unable to load dynamic library 'php_wincache.dll'?

橙三吉。 提交于 2020-06-27 17:49:41
问题 Because I already use ASP.NET I decided to use PHP on IIS, I install it using Wep PI but when I trying to install Composer he fails with PHP settings error. I tried to change the extension_dir to absolute and uncommented php_wincache extension in php.ini but none of my solutions works C:\Program Files (x86)\iis express\PHP\v7.2\php.exe The php.ini used by your command-line PHP is: C:\Program Files (x86)\iis express\PHP\v7.2\php.ini A setting in your php.ini could be causing the problem:

PHP HTTP extension on Docker alpine image

余生颓废 提交于 2020-06-17 04:13:59
问题 I am trying to install/enable the PHP http extension on my PHP alpine image. My composer.json file for my application contains "ext-http": "*" , hence my goal. My Dockerfile (relevant portions) is as follows: # PHP-FPM Base Image FROM php:7.2.26-fpm-alpine # Install PHP extensions RUN apk add --update --virtual .build-deps autoconf g++ make zlib-dev curl-dev \ && pecl install raphf propro \ && docker-php-ext-enable raphf propro \ && pecl install pecl_http \ && echo -e "extension=raphf.so

PHP HTTP extension on Docker alpine image

北城以北 提交于 2020-06-17 04:13:45
问题 I am trying to install/enable the PHP http extension on my PHP alpine image. My composer.json file for my application contains "ext-http": "*" , hence my goal. My Dockerfile (relevant portions) is as follows: # PHP-FPM Base Image FROM php:7.2.26-fpm-alpine # Install PHP extensions RUN apk add --update --virtual .build-deps autoconf g++ make zlib-dev curl-dev \ && pecl install raphf propro \ && docker-php-ext-enable raphf propro \ && pecl install pecl_http \ && echo -e "extension=raphf.so

How composer `extra.symfony.require` restriction is enforced?

我们两清 提交于 2020-06-16 09:25:03
问题 Let's say I have a Symfony v4.4 (Flex) project with the following block in the composer.json : "extra": { "symfony": { "allow-contrib": false, "require": "4.4.*" } } As expected, it restricts the Symfony core packages to stick to the v4.4 version. symfony/monolog-bridge package respects it, so you cannot install symfony/monolog-bridge ~4.3.0 or ^5.0 . Yet you can install symfony/monolog-bundle ~3.5.0 , which is also expected, given it's just a bundle that is not part of the core Symfony