What’s the recommended way to run php artisan tenants:migrate using Laravel Tenancy with automations enabled?

[Mahoke]

I'm using the serversideup/docker-php image to run a Laravel app that uses stancl/tenancy for multi-tenant database support.

The default automation script (entrypoint.d/50-laravel-automations.sh) runs central migrations via php artisan migrate --force and then proceeds to cache config, routes, views, etc. (link to script).

However, Laravel Tenancy also requires tenant-specific migrations via:

php artisan tenants:migrate --force

Question

Is there an officially supported or recommended way for inserting additional artisan commands — specifically tenants:migrate — before caching takes place?

Should i disable automations, duplicate the entire (entrypoint.d/50-laravel-automations.sh) and run artisan tenants:migrate in that file?

Feature Suggestion

It would be awesome if the image supported additional artisan commands through an environment variable like:

AUTORUN_LARAVEL_CUSTOM_COMMANDS="tenants:migrate --force; app:my-other-command-1; app:my-other-command-2"

#or AUTORUN_LARAVEL_POST_MIGRATE_COMMANDS

// Maybe like:
...
            echo "🚀 Running migrations..."
            if [ "${AUTORUN_LARAVEL_MIGRATION_ISOLATION:=false}" = "true" ]; then
                php "$APP_BASE_DIR/artisan" migrate --force --isolated
            else
                php "$APP_BASE_DIR/artisan" migrate --force
            fi
        fi

        ############################################################################
        # Custom post-migrate Artisan commands
        ############################################################################
        if [ -n "${AUTORUN_LARAVEL_CUSTOM_COMMANDS}" ]; then
            echo "🚀 Running custom Artisan commands: $AUTORUN_LARAVEL_CUSTOM_COMMANDS"
            IFS=";" read -ra COMMANDS <<< "$AUTORUN_LARAVEL_CUSTOM_COMMANDS"
            for cmd in "${COMMANDS[@]}"; do
                echo "➡️ php artisan $cmd"
                php "$APP_BASE_DIR/artisan" $cmd
            done
        fi
...

…which could be executed right after the main migrate --force step and before caching starts.

This would allow tenancy and other similar packages to hook into the automation cleanly.