Forge Deployment failing on >php artisan optimize

Did you setup your database before the first deployment? Also make sure your .env is setup correctly, with APP_ENV=production

Following the guide i thought this would be setup when i deploy. I have setup the .env file.

I have also tried creating a new DB and user and adding these details into the .env file but i get the same error.

Tried manually doing php artisan migrate and also get the same error.

Hm, if you're using localhost in your .env file, try replace it with 127.0.0.01

DB_HOST=127.0.0.1

You need to run php artisan config:clear after changing the config files because the config is cached. Then, you can run php artisan migrate.

Just tried php artisan config:clear

I still get the same error.

php artisan migrate
[Illuminate\Database\QueryException]                                         

SQLSTATE[HY000] [2002] No such file or directory (SQL: select * from inform ation_schema.tables where table_schema = energya and table_name = migration s)

It seems to be able to connect as it is throwing No such file or directory not a connection error.

Make syre your forge user for the DB values are correct in .env. I use localhost on all of my forge servers. Sometimes, after changing the config and clearing cache, I have had issues continue until I redeployed the project. Then, I was able to migrate.

See if this helps..

Edit config/database.php and add the last line as example shown below..

        'mysql' => [
            'driver' => 'mysql',
            'host' => env('DB_HOST', 'localhost'),
            'port' => env('DB_PORT', '3306'),
            'database' => env('DB_DATABASE', 'forge'),
            'username' => env('DB_USERNAME', 'forge'),
            'password' => env('DB_PASSWORD', ''),
            'charset' => 'utf8',
            'collation' => 'utf8_unicode_ci',
            'prefix' => '',
            'strict' => true,
            'engine' => null,
            'unix_socket' => '/tmp/mysql.sock', // <<-- add this line
        ],

Just tried adding this-

'unix_socket' => '/tmp/mysql.sock', // <<-- add this line

Still the same error. I also tried to create another database on the server and use the details for that. Also tried importing the database from my local machine to see if having existing tables would make a different.

Still just get the same error.

@jayscottelliott with the /tmp/mysql.sock in place try run php artisan config:clear and composer dump-autload and then try to migrate again..

If it doesn't work, log in to Forge, at the bottom right there is a Help > Contact us button. I'm running out of ideas :(

Thanks for you help. I have lodged with forge support. Will post the solution if I get it fixed.

I know the post is old but possible issue is your AppServiceProvider.

@EE More info plz ?

yeah @EE little explanation would be nice.

@itsali @develalfy in my case I was running query on my service provider like below. It was giving me error without using try catch . So with wrapping my query with try catch I solved my issue.

        try {
            if (Schema::hasTable('settings')) {
                $settings = Setting::pluck('value', 'key')->toArray();
                if (isset($settings['media_lock'])) {
                    if ($settings['media_lock'] == 'false') {
                        //do something
                    }else{
                         //do other things
                    }
                }
            }
        } catch (\Illuminate\Database\QueryException $e) {
            app('log')->error($e->getMessage());
        }

The same issue here, I had this going on:

public function boot()
    {
        Schema::defaultStringLength(191);

        Gallery::deleting(function ($gallery) {
            \Storage::delete('galleries/' . $gallery->id);
        });

        View::share('recentArticles', $this->getRecentArticles());
    }

My AppServiceProvider was trying to grab articles from a database that hadn't been set up yet, and in the Forge pipeline, .env is generated after a successful first build. I wonder if there's a better way to do a first build on Forge...

I've just linked my GitHub to a shared private repo on Forge, getting the same error.

@firemaps If you are the repo owner, then permissions should be correct. Go into the profile settings of Forge and refresh your github token. Sometimes, that will fix the issue. If you are not the listed owner of the repo, then have the owner give you full permissions on that repo.