php-console | 🖥 PHP CLI application library , provide console options | Command Line Interface library

I copied your composer.json to my local environment and ran composer update and had the same results. The problem is, that the class Sensio\Bundle\DistributionBundle\Composer\ScriptHandler does not exist with your config. So I executed composer require sensio/distribution-bundle, but then I got a version conflict:

I used this and It works for me.

From documentation composer suggests :

Lists all packages suggested by currently installed set of packages. You can optionally pass one or multiple package names in the format of vendor/package to limit output to suggestions made by those packages only.

You need to change the version of laravel/framework in composer.json (back) to ^6.2:

$url is an array; parse_url is returning an associative array. The url key in the configuration should be a string representing a URL, not an array. You are assigning 'url' => $url,, so 'url' is an array, not a string.

If you want to use the url you only need to set that key, it will parse the rest of the information from that URL you are given for you.

"Some managed database providers such as Heroku provide a single database "URL" that contains all of the connection information for the database in a single string."

"For convenience, Laravel supports these URLs as an alternative to configuring your database with multiple configuration options. If the url (or corresponding DATABASE_URL environment variable) configuration option is present, it will be used to extract the database connection and credential information."

Laravel 5.8 Docs - Database - Configuration - Configuration Using URLs

A fresh Laravel install comes with a bootstrap/cache/.gitignore file. Its presence (and contents) in the respository ensures that the directory exists in a deployment, but that nothing else within that directory winds up in source control.

The error you're receiving indicates that you didn't check it into your repository (or removed it for some reason). Checking it in should clear up the message, as the folder will exist for your app to write to it.

There are several other instances of this, like storage/logs, a variety of subfolders of storage/framework, etc. If you receive similar errors in these directories, the same fix applies.

The docs on the GitHub for that is wrong. I looked at the source. That class is in namespace "Adyen\Service".

Change your code as follows:

I solved it doing composer install instead of composer update.

Still no idea about why it didn't work, but at least it works now...

For people trying (as I used to) to do composer update in a context of production, don't:

What are the differences between composer update and composer install?

When to install and when to update

• composer update is mostly used in the 'development phase', to upgrade our project packages according to what we have specified in the composer.json file,

• composer install is primarily used in the 'deploying phase' to install our application on a production server or on a testing environment, using the same dependencies stored in the composer.lock file created by composer update.

And a nice diagram here.

A discussion about curl error was posted here for reference: SSH Curl doesn't work when URL is accessible in browser

For french developers using SSH with a shared hosting pro at OVH, the support says external calls like curl are disabled in ssh, but obviously I could do curl https://packagist.org/packages.json. When they tried themselves, they got an error like action forbidden or something like that. It doesn't make any sense.

It looks like your composer packages got out of sync.

To force a refresh delete the vendor folder also delete composer.lock and then run

composer install

It will download everything again, rebuild your vendor and make sure Phinx and Symphony are in sync again.

After you do this, you run your migrations again and see what happens.

This statement of yours

"I dropped all tables and hoped that it will just re-run the migrations as before."

worries me a bit, because the Phinx migration manger keeps its log in the database in a table called phinxlog (sometimes prefixed with a plugin name if you're talking about a plugin). If you deleted that then phix does not know what migrations did you run already and which ones are new. To fix this you may need to mark some of the earlier migrations are migrated so phinx does not attempt to do things that were already done.