if it was not committed to the project), then composer install also effectively performs a composer update. Similarly, if you do not currently have a composer.lock file (e.g. Running composer update also performs a composer install, and if you do not currently have a vendor folder (normal if you have a fresh checkout of a project), then it will create one, and also overwrite any composer.lock file you already have, updating package versions tagged in it, and this is what is potentially dangerous. In that case, you can still use composer: run it locally (an environment that has no such restrictions), and upload the local vendor folder it generates along with all your other PHP scripts. because it's shared and they have no shell access). ![]() ![]() ![]() I often see complaints that people can't use composer because they can't run it on their server (e.g. To clarify further – you should probably only ever run composer update locally, never on your server as it is reasonably likely to break apps in production. If your code is tested with your current package versions then running update may cause breakages which may require further work and testing, so don't run update unless you have a specific reason to and understand exactly what it means. The autoload.php you found in C:\Windows\SysWOW64\vendor\autoload.php is probably a global composer installation – where you'll usually put things like phpcs, phpunit, phpmd etc.Ĭomposer update is not the same thing, and probably not what you want to use. For example the example scripts in PHPMailer are in examples/, below the project root, so the correct relative path to load the composer autoloader from there would be. What you're missing is running composer install, which will import your packages and create the vendor folder, along with the autoload script.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |