Replies: 4 comments
-
Seems it did run the configure script even though it through an error. |
Beta Was this translation helpful? Give feedback.
-
I tried it and didn't get an error... Feel free to send a PR should you investigate this further. |
Beta Was this translation helpful? Give feedback.
-
This happens if you run it once, and it fails when it tries to run composer install, and for example, the PHP version is wrong. In my case I had PHP 8.3 as standard in my DDEV configuration, and I needed PHP 8.4. After updating to PHP 8.4, I ran it again and this occurred, because all the files had already replaced all instances in all files, so the files array returned was empty. Easy fix, added an if around the file replace part. Ran it again and I did it all to the end. |
Beta Was this translation helpful? Give feedback.
-
run to the same issue while using docker (wodby/php:8.4)
compose file:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I've installed this template into a new repository and have checked it out locally and now am attempting to run the
php ./configure.php
step.I've filled out
And have the following selected:
Packages & Utilities
Use Laravel/Pint : yes
Use Larastan/PhpStan : yes
Use Dependabot : yes
Use Ray App : yes
Use Auto-Changelog : yes
This script will replace the above values in all relevant files in the project directory.
Modify files? (Y/n): Y
And i get the following
Fatal error: Uncaught ValueError: Path cannot be empty in ~//configure.php:64
Stack trace:
#0 ~//configure.php(64): file_get_contents('')
#1 ~///configure.php(306): replace_in_file('', Array)
#2 {main}
thrown in ~//configure.php on line 64
I'm running PHP 8.4 via laravel Herd on Mac OS 14.2.1
Beta Was this translation helpful? Give feedback.
All reactions