Error after change from 5.3 to 5.4 laravel

@raffelustig no clue why that fails. Try temporarily removing the command and finish upgrading. Then add it back in and see if you can do composer update

"post-install-cmd": [
            "Illuminate\Foundation\ComposerScripts::postInstall",
            "php artisan optimize"
        ],

@raffelustig so now you are working on npm? Not sure how that is related to upgrading laravel?

@Sinnbeck The system is sitting in a docker environment and there is several commands to get it up and running. Such as this:

if [ ! -f ".dont_install" ]; then

echo Install started

composer install  --no-ansi --no-dev --no-interaction --no-progress --no-scripts --optimize-autoloader

cp .env.docker .env
php artisan passport:install
php artisan key:generate
php vendor/bin/optimus spark|grep :|sed -e 's/\(.*\)/\U/' -e 's/: /=/' -e 's/^/OPTIMUS_/' >> .env

npm install && gulp
php artisan config:clear
php artisan migrate
php artisan db:seed
#php artisan passport:install|grep t:|awk '/t:/ { getline; sub(/.*:.* /,"API_CLIENT_SECRET="); print LARACASTS_SNIPPET_PLACEHOLDER;}' >> .env
php artisan passport:client --password|grep t:|awk '/t:/ { getline; sub(/.*:.* /,"API_CLIENT_SECRET="); print LARACASTS_SNIPPET_PLACEHOLDER;}' >> .env

mkdir -p storage/app/public
mkdir -p storage/framework/cache
mkdir -p storage/framework/sessions
mkdir -p storage/framework/views
mkdir -p storage/logs

chmod 777 -R storage

chown www-data:www-data -R storage
chmod 600 storage/oauth-*.key

touch .dont_install

echo Install completed

fi

echo Starting php-fpm

php-fpm -F -R

@raffelustig ok. Let us know once your docker issues are fixed so we can get back to updating laravel :)

@Sinnbeck As I think I said earlier I ordered a Laravel Docker Shift for $49 with no success yet. I have the 5.4 to 5.5 waiting also if I succeed with this.

@raffelustig ouch that sucks :(

@Sinnbeck so you think it's a docker issue?

@Sinnbeck If you want to look at the site (the one sitting in a server, not docker version): https://test.webshooter.se Pistol competition site

@raffelustig no the issue seems to be with the docker image trying to install yarn and failing. I assume it's another docker image that you posted as the failing command is RUN npm install -g yarn

@Sinnbeck If I do this:

Ralphs-MacBook:webshooter_web ralph$ 
Ralphs-MacBook:webshooter_web ralph$ npm install -g yarn

changed 1 package, and audited 2 packages in 2s

found 0 vulnerabilities
Ralphs-MacBook:webshooter_web ralph$ 

it works

@raffelustig yes its docker that is failing. Is it a docker image from shift or your own?

Ralphs-MacBook:webshooter_web ralph$ node -v
v17.1.0
Ralphs-MacBook:webshooter_web ralph$ npm -v
8.1.4

@Sinnbeck my own

@raffelustig then I assume you are getting the error building your images. I assume you run something like docker-compose up

@Sinnbeck docker compose up --build yes

@raffelustig then check your docker image files. One of them must have the yarn installation

@Sinnbeck I'll have a look

@raffelustig image file. Not image as such. Perhaps create a new thread regarding your docker images not working. As you can see from the error, the problem is with npm, and not php/laravel

@Sinnbeck I have these:

redis		alpine	3900abf41552	about 8 hours ago	32.38 MB	
nginx		alpine	b46db85084b8	17 days ago	23.2 MB	
maildev/maildev		latest	9259e42215ab	over 1 year ago	86.62 MB	
mysql		5.7.22	6bb891430fb6	over 3 years ago	371.94 MB

Can't see any yarn anywhere

@raffelustig those are running containers. Your problem is building an image which can then run as a container

@Sinnbeck aha

@Sinnbeck No, those are images on disk, no containers are present.

@raffelustig well still the issue is building the image.

The number here shows what layer it is building of the image (layer 9 out of 16)

9/16] RUN npm install -g yarn

@Sinnbeck I understand. Well I don't have a clue what to do with that.

It talkes about a log

#26 16.02 npm ERR! A complete log of this run can be found in:
#26 16.02 npm ERR!     /root/.npm/_logs/2021-11-30T19_47_00_321Z-debug.log

I can not find that anywhere

@Sinnbeck Now I can not do anything. I changed over to my master branch and it complains about yarn also. So now it's something in npm or node versions.

Do I have to downgrade npm or node or both?

@raffelustig have you considered a new version and migrate models, controllers, etc over to a new install.

@jlrdw I have tried that but as the system is soooo complicated it's not easy.

@jlrdw Do you have a suggestion on how and in what order I shall copy the different parts over to the new, empty laravel? I'm not sure I have done it in proper order. And how to test during?

@raffelustig see here https://laravel.com/docs/8.x/upgrade

But read each upgrade guide for every version.

Whether or not you are upgrading or migrating stuff over the upgrade guides shows you the changes that you need to be aware of.

One time I went from a 5.5 to 6.1, only took about 30 minutes. And that was migrating stuff to a new application not an upgrade.

@raffelustig What would do for copy/migrate strategy is make a git branch with the LTS version of Laravel cleanly installed to it, a branch of your master with edited areas like app directory resources etc, and then I would merge to force a conflict. The conflict will flag all your goodies. And then you can work it in methodically. It really does sound like a pain but not as bad as upgrading from each version until 9x LTS.

The easiest thing to do just copy and paste the logic into a clean laravel install and then upgrade php or SQL where necessary. Newer versions of Laravel are recommended to Jetstream, which I agree, but I think UI is better for this.

Also, you got docker. They say its good for legacy apps because you can run older versions of ubuntu