On App Platform, Where do I put db migration and other commands, run or buid?

Posted March 4, 2021 1.3k views
LaravelDigitalOcean App Platform

I just started working with App Platform and I am unsure which commands I should be adding in Run vs Build steps.

I am deploying a Laravel App and I need to run DB migrations, route caching, & config caching.

php artisan migrate --force
# Clear caches
php artisan cache:clear

# Clear expired password reset tokens
php artisan auth:clear-resets

# Clear and cache routes
php artisan route:cache

# Clear and cache config
php artisan config:cache

# Clear and cache views
php artisan view:cache

Should these be Build Commands after my composer install or should they be Run Commands before I run heroky-php-apahce2?

Or does it matter?

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
1 answer

Hi there,

I would usually put then in the run section.

Here is a cool 1 hour long video that shows how to build and deploy Laravel on the App platform:

At minute 38:00 you can see the migration part.

Another good resource is this tutorial here that shows you how to use the doctl command line to deploy Laravel to the App platform:

In that article, Erika uses a separate Job component for the migrations.

Hope that this helps!

  • Thanks for the reply. The Run section seemed liked the correct spot but I hadn’t read any documentation or blog post that mentioned it. The articles I read had just ran migrate from the console tab.

    The Doctl article looks interesting, I may give that a shot as we deploy more sites.

    Thank you,