Скачать или смотреть Solving Database connection [mysql] not configured Error in Laravel/Vue.js with MongoDB on Heroku

Discover how to fix the `Database connection [mysql] not configured` error when deploying your Laravel/Vue.js app with MongoDB on Heroku, and ensure a smooth deployment process.
---
This video is based on the question https://stackoverflow.com/q/67570090/ asked by the user 'Liiisey' ( https://stackoverflow.com/u/14162776/ ) and on the answer https://stackoverflow.com/a/67820335/ provided by the user 'Liiisey' ( https://stackoverflow.com/u/14162776/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Deployment error with Laravel/Vue.js app and MongoDB on Heroku

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Troubleshooting Deployment Errors in Laravel/Vue.js with MongoDB on Heroku

Deploying a Laravel/Vue.js application that uses MongoDB on Heroku can sometimes lead to frustrating errors. One common issue is the deployment error related to database connection configurations, specifically the error message: "Database connection [mysql] not configured." This guide aims to demystify that error and provide a clear solution so you can resume your deployment smoothly.

Understanding the Problem

When you push your Laravel/Vue.js application to Heroku, you might encounter an error that looks something like this:

[[See Video to Reveal this Text or Code Snippet]]

This error indicates that your application is looking for a MySQL database configuration. Since you're using MongoDB, there should be no reference to MySQL in your application.

Why It Happens

The root cause of this issue typically lies in your configuration files. During the deployment process, Laravel runs some artisan commands, one of which attempts to configure your database connections based on the .env settings. If there are any references to MySQL in configuration files, particularly where the application tries to establish a database connection, you'll encounter this error.

Diagnosing the Error

Here's a step-by-step guide to identifying and correcting the issue:

Check Configuration Files: Your two primary configuration sources are:

config/database.php: This file should contain the MongoDB configuration settings.

.env file: Ensure that the settings here are also pointing towards MongoDB.

Look for MySQL References: Inspect other configuration files that may inadvertently refer to MySQL. One common culprits are files such as config/queue.php.

Heroku Logs: Utilize Heroku's debugging tools. Running heroku logs --tail will give you a live view of what happens during deployment, which can reveal additional context for your error.

The Solution: Fixing the Configuration

Once you've identified the MySQL references, you need to fix them. Here's how you can do it:

Step 1: Update config/queue.php

Locate the config/queue.php file in your project, and check for any database references that may still be pointing to MySQL. For instance, you may find a section that looks like this:

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Change mysql to mongodb

Replace the mysql setting in the database parameter with mongodb. After modification, your configuration should look like this:

[[See Video to Reveal this Text or Code Snippet]]

Step 3: Clear Configuration Cache

After making changes to your configuration files, it's essential to clear your old settings by running:

[[See Video to Reveal this Text or Code Snippet]]

This command forces Laravel to re-read the configuration files and apply any updates you've made.

Step 4: Redeploy to Heroku

With the changes made and the configuration cache cleared, it's time to push your application back to Heroku. Test the deployment process:

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

By correcting references to MySQL in your Laravel application's configuration, particularly in files like config/queue.php, you can effectively resolve the Database connection [mysql] not configured error when deploying on Heroku. Make sure your application is entirely pointing towards your MongoDB settings. With a bit of troubleshooting, you’ll be back on track to deploying your app without any hitches.

Thank you for following along! For additional questions or support related to Laravel, Vue.js, or MongoDB, feel free to reach out in the comments below.