How can I solve this「Can't open perl script "/assets/prestart.pl": No such file or directory
Project ID: 4358cb63-ffcc-4ed0-8d93-a94e494345f2
deployment ID: fe64d2d
I'm trying to deploy a Laravel application.
Builder: Nixpacks
Providers: Php
Custom Build Command:
npm run build && composer install --optimize-autoloader --no-dev && php artisan config:cache && php artisan migrate --force
Custom Start Command: perl /assets/prestart.pl /assets/nginx.template.conf /nginx.conf && (php-fpm -y /assets/php-fpm.conf & nginx -c /nginx.conf & php artisan inertia:start-ssr)
Build Logs is end 「Publish time: 11.75 seconds」ok,
but Deploy Logs is Can't open perl script "/assets/prestart.pl": No such file or directory
Solution:Jump to solution
the php provider has changed and it no longer includes perl.
please undo your custom command so you can copy down the new default command, then make your changes to the new command...
8 Replies
Project ID:
4358cb63-ffcc-4ed0-8d93-a94e494345f2
Solution
the php provider has changed and it no longer includes perl.
please undo your custom command so you can copy down the new default command, then make your changes to the new command
I will try. thanks!
I removed Custom Start Command, now partially working. thank you.
Another problem is that Laravel doesn't seem to be working with SSR (Twitter cards don't seem to be displayed. example : https://godotplayer.com/games/yozora_maker_4x). Is there any workaround?
i assume something that you where running in your custom command fixed this before?
before, i include custom command
Deploy Logs displayed , but Web application does works. (displayed
php artisan inertia:start-ssr
, It used to work as SSR.
Now, i try 2 pattern.
* Custom Start Command empty : Web application works, but does not display Twitter cards, etc.
* Custom Start Command setting only php artisan inertia:start-ssr
:Deploy Logs displayed , but Web application does works. (displayed
Application failed to respond
)please see my original message
Sorry, I didn't understand English very wel.
From the Build log, we could probably figure out the default start command. Thanks!
feel free to translate into your language! 🙂