Laravel Cloud Failed Deployment (database) | Laravel | Page 1

bronze folio Apr 18, 2025, 6:30 AM

#

Hello,

I am currently migrating from Vapor to Cloud. I added the github repo to Cloud, deleted the manifest.yaml and vapor.yml files, and added a private mysql database in Cloud. The database name is "<database_name>" (for the purposes of this post).

I am currently getting the following when deploying the application:

Preparing build environment succeeds
Running build commands succeeds
Pushing application succeeds
Preparing deploy environment succeeds
Running deploy commands fails: In Connection.php: Unknown database '<database_name>'

Has anyone seen this before? Have any ideas on how to resolve the issue? Any ideas are greatly appreciated!

alpine stump Apr 18, 2025, 10:33 AM

#

Check the DB_CONNECTION in the .env file, or maybe in your Connection.php file. Verify it's mysql(or the driver you are using).

tawdry island Apr 18, 2025, 10:36 AM

#

What do you env settings in Cloud look like? Laravel Cloud injects those credentials if the DB is attached to the app/environment

#

So you might be overwriting them, thus causing it to not be able to connect

bronze folio Apr 18, 2025, 3:31 PM

#

alpine stump Check the DB_CONNECTION in the .env file, or maybe in your Connection.php file. ...

There is no .env file -- those variables are stored in the Custom environment variables and Injected variables fields in the settings in Laravel Cloud. I have not added any custom env variables, and the injected variables are managed by Cloud -- so I cannot change them.

I do not have a Connection.php file.

bronze folio Apr 18, 2025, 3:33 PM

#

tawdry island What do you env settings in Cloud look like? Laravel Cloud injects those credent...

This is what is incredibly strange. I have not modified any env variables. The only custom env var is the APP_KEY, which was auto-generated. There is then the full DB_* info (DB_CONNECTION, DB_DATABASE, etc)

bronze folio Apr 18, 2025, 3:33 PM

#

tawdry island So you might be overwriting them, thus causing it to not be able to connect

So to the point I just wrote, I have not modified any env variables

#

But like... these are the reasons I am so confused. All env vars were auto-injected by Cloud, yet, it is giving me a seemingly-related error.

alpine stump Apr 18, 2025, 3:39 PM

#

Have your tried refreshing cache?
php artisan config:clear
php artisan config:cache

bronze folio Apr 18, 2025, 4:03 PM

#

When I try to run the commands via the Commands tab, it says I am unable to since I have no active deployment.

tawdry island Apr 18, 2025, 4:22 PM

#

Yeah, think those commands wouldn't really have an effect in Cloud anyways

#Laravel Cloud Failed Deployment (database)