Forge Zero Downtime Deployment

Before I start, yes I know I could utilize something like Envoyer for a zero downtime deployment, but it's just not affordable for me at this time to add another subscription to my monthly expenses. I have a deployment script that works pretty well I think, I'm mostly looking for feedback/advice on what I could do better on it, especially as the app grows.

Here is my working script right now:

cd /home/forge

PROJECT_NAME="$FORGE_SITE_PATH"
PROJECT_REPO="[email protected]:my-username/my-repo.git"
RELEASES_KEPT=3
RELEASE=$(date +"%Y-%m-%d-%H-%M-%S")

# Copy the current .env file.
cp $PROJECT_NAME"/.env" $PROJECT_NAME".env"

# Create a project-name-releases directory if it does not exist.
if [ ! -d $PROJECT_NAME"-releases" ]
then
  mkdir $PROJECT_NAME"-releases"
fi

# Create our new release.
cd $PROJECT_NAME"-releases"
git clone $PROJECT_REPO $RELEASE

cd $RELEASE

# Install dependencies
$FORGE_COMPOSER install --no-interaction --prefer-dist --optimize-autoloader

# Move in the current .env file and clean up.
cp -af "../../"$PROJECT_NAME".env" ".env"
rm "../../"$PROJECT_NAME".env"

# Compile our assets.
npm install
npm run build

# Now that our scripts are compiled, we can safely remove the node directory.
rm -rf node_modules

# Copy the current storage directory.
cp -r $"../../"PROJECT_NAME"/storage" "../../"$PROJECT_NAME"-storage"

# Move in the current storage directory and clean up.
rm -rf storage
mv "../../"$PROJECT_NAME"-storage" storage

if [ -f artisan ]
then
  $FORGE_COMPOSER update-permissions # Seed any new permissions
  $FORGE_PHP artisan route:cache
  $FORGE_PHP artisan view:cache
  $FORGE_PHP artisan event:cache
  $FORGE_PHP artisan horizon:terminate
  $FORGE_PHP artisan storage:link
  $FORGE_PHP artisan config:cache
fi

# Clean up old releases.
cd ..
rm -rf `ls -1 | sort -r | tail -n +$((RELEASES_KEPT+1))`

cd /home/forge

# Remove the project directory if it exists.
if [ -d $PROJECT_NAME ]
then
  rm -rf $PROJECT_NAME
fi

# Re-link our new release.
ln -sfn $PROJECT_NAME"-releases/"$RELEASE $PROJECT_NAME

# Reload PHP-FPM.
( flock -w 10 9 || exit 1
    echo 'Restarting FPM...'; sudo -S service $FORGE_PHP_FPM reload ) 9>/tmp/fpmlock

I do have one concern about this script, and it's about the storage directory. I have some custom disks I use for user uploads that are stored in the storage directory. My concern is what if a user happens to be uploading a file at the same time I'm moving the storage directory during a deployment. How do I make sure I don't lose that file in the process? This is mostly why I'm installing and compiling my npm assets before I copy over the storage directory since it can take a while to do that sometimes.