Level 122
Why do you need to use other than the default?
You can just run optimize instead of poinlessly clearing caches and then caching (which clears anyway)
Aug 22, 2024
5
Level 4
Forge deploy script
Hi, what is the best script to use in Forge? Ive seen:
cd /home/forge/app.thillow.co.uk
git pull origin $FORGE_SITE_BRANCH
$FORGE_COMPOSER install --no-dev --no-interaction --prefer-dist --optimize-autoloader
( flock -w 10 9 || exit 1
echo 'Restarting FPM...'; sudo -S service $FORGE_PHP_FPM reload ) 9>/tmp/fpmlock
if [ -f artisan ]; then
$FORGE_PHP artisan migrate --force
fi
# clear any existing cache
php artisan view:clear
php artisan route:clear
php artisan event:clear
php artisan config:clear
php artisan auth:clear-resets
# cache everything that's possible
php artisan view:cache
php artisan route:cache
php artisan event:cache
php artisan config:cache
npm i && npm run build
$FORGE_PHP artisan horizon:terminate
Is this optimal? Thanks
Level 4
@Snapey Hi, so should you run optimize in script?
npm i && npm run build was not in the defaults, should i keep this? Sorry for the noob questions.
Level 80
@Cushty You’d run npm i && npm run build if you have assets you need building with Vite.
Level 4
@martinbean thank mate, yeah I ran with those npm i && npm run build, just checking if I should also add PHP artisan optimize. Thanks
Level 80
@Cushty As @snapey says, they just call all the *:cache commands any way:
And each of those *:cache commands automatically clear before running:
So basically, php artisan optimize is just a shorthand that will clear all those caches, and then re-cache those assets.
Given that you’re (hopefully) not going to be editing things like views, routes, and configuration on your production server between deployments, it makes sense to cache them to get any performance boost. But you should never run those commands outside of your Forge/production environment.
Please or to participate in this conversation.