Skip to main content
Some migration operations are destructive, which means they may cause you to lose data. All Laravel Cloud environments default to APP_ENV=production, so you may run into issues when you run one-off migrations from the Commands tab of your environment panel. These commands are not interactive, so a command fails if it tries to prompt you for input. This failure happens most often when you run migrations in a production environment.
If you accept the risks of running migrations in a production environment, pass a flag to bypass the production environment warning.
Append the --force flag to bypass the production prompt:
Related commands that may also require the --force flag include:

​
Customizing your APP_ENV

If you are working on a non-production environment, consider overriding the APP_ENV variable in your environment’s custom environment variables to match the environment’s purpose. Non-production environments do not trigger the production warning.