Fix Production Command Failures

Some migration operations are destructive, which means they may cause you to lose data. As all Laravel Cloud environments default to APP_ENV=production, you may run into issues running migrations in an ad-hoc manner using the “Commands” tab from your environment panel. Since these commands do not support interactivity, the command will fail if it attempts to prompt you for input. This happens most commonly when attempting to run migrations in a production environment.

                           APPLICATION IN PRODUCTION.

   WARN  Command cancelled.

If you are comfortable with the risks associated with running migrations in a production environment, pass a flag to bypass the production environment warning.

Laravel
Symfony

Append the --force flag to bypass the production prompt:

php artisan migrate --force

Related commands which may also require the --force flag include:

php artisan migrate:fresh --force
php artisan migrate:refresh --force
php artisan db:seed --force

Append the --no-interaction flag to bypass the production prompt:

php bin/console doctrine:migrations:migrate --no-interaction

Related commands which may also require the --no-interaction flag include:

php bin/console doctrine:migrations:migrate --no-interaction --allow-no-migration
php bin/console doctrine:schema:update --no-interaction --force

Customizing your `APP_ENV`

If you are working on a non-production environment, you may consider overwriting your APP_ENV environment variable in your environment’s Custom Environment Variables to better match your environment’s purpose. Non-production environments will not trigger the same warnings as described above.

APP_ENV=development

Environment Not Sleeping SQLite Support

⌘I

Getting started

Guides

Migration guides

Troubleshooting

Fix Production Command Failures

Customizing your `APP_ENV`

​Customizing your APP_ENV

Customizing your `APP_ENV`