Not able to run laravel migrations in the release build on build server

[lexjwa]

We have a build server on we build a new build and store it under another directory on build server.
server/path-to-project/.build/releases/1

After creating the build, we intent to run unit tests or manually test our new build on the build server before we deploy to many application servers at once. To accomplish this we need to run migrations and seeders, of course also need to generate application key every time we make a build.

We are able to dynamically create a new database for each build, cp or touch the new .env file into server/path-to-project/.build/releases/1 and write new database credentials into .env file but when we run

run('{{bin/php}} {{release_or_current_path}}/artisan migrate --force');
or
run('php artisan migrate');
or invoke
task('artisan:migrate', artisan('migrate --force', ['skipIfNoEnv']));

in deploy.php it does not pickup the new database we are creating, it rather run migrations into actual build project we are building from, which is server/path-to-project/ but not in server/path-to-project/.build/releases/1

We cleared cache and configuration before running the any of those commands but seems whatever we initiate it, the php artisan migrate process the wrong .env.

If we cd into server/path-to-project/.build/releases/1 and run php artisan migrate it works fine but we need to do it via the deploy.php when building each build.

Deployer version: "deployer/deployer": "^7.0"

Any perspective or guidance is appreciated!

[antonmedv]

Please show your deploy.php.

[antonmedv]

Well. Difficult to tell))

[nathan-io]

The root issue seems to be that after we remove the .env symlink from the current release directory and replace it with an actual .env file, artisan is ignoring the new local env file and continues using a different environment.

This happens ​even if we php artisan config:clear from the current release directory after swapping .env files.

So when executing run('php artisan migrate'); (as one example), it's still using the loaded environment variables from /home/deployer/.env (the .env of the repo where Deployer lives) rather than the local .env in the current release folder.

Yet the contents of /home/deployer/.build/current/.env are as expected, which is why php artisan migrate or other commands work if you manually run them from that folder outside of the deploy.php script.

Out of curiosity, I tried moving the php artisan migrate command to a bash script, them modified deploy.php to copy that script into the new release folder and run it there. Same result.

---

Not sure if this matters, but we are not building and deploying the same repo that Deployer lives in (deployer). We are defining a different repo.

The make:database and write:env commands live in the repo we're deploying, not deployer itself.

[lorisleiva]

Could this be an OPCache issue because of the symlinks? Are you using the real path in your NGINX config? Note that if you're using Forge to deploy, it's not the case by default.

fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
fastcgi_param DOCUMENT_ROOT $realpath_root;

[nathan-io]

Thanks for the tip @lorisleiva !

Our build server was provisioned by Forge, though we're not using the "Deploy" features of Forge to do any deployment in this case.

From what I can see in the Forge dashboard and within the PHP CLI config file, Opcache is not currently enabled.

I updated the Nginx config of the site we're deploying from like so:

    location ~ \.php$ {
        fastcgi_split_path_info ^(.+\.php)(/.+)$;
        fastcgi_pass unix:/var/run/php/php8.0-fpm.sock;
        fastcgi_index index.php;
        include fastcgi_params;
        
        fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
        fastcgi_param DOCUMENT_ROOT $realpath_root;        
    }

Restarted Nginx, but unfortunately this made no difference.

I also tried this in deploy.php

    run('rm .env');
    run('cp '.$build_env.' .env');
    run('sudo /usr/sbin/service php8.0-fpm reload');
    run('sudo /usr/sbin/service php8.0-fpm restart');
    run('sudo /usr/sbin/service nginx restart');
    run('php artisan config:clear');
    run('php artisan write:env DB_DATABASE platform{{release_name}}');
    run('php artisan write:env APP_ENV local');

No difference with that, unfortunately. (The server is currently configured to allow those three service commands without a password.)

This comment has some interesting discussion about this, but I wonder how Nginx or PHP-FPM could be the issue here.

---

As a workaround, we're going to try creating the new .env as .env.build and passing ---env=build to the artisan commands. I hope that works.

[antonmedv]

BTW, Deployer has a new recipe called provision.

It can provision a host and will configure php and server to correctly work with realpath. So no phpfpm reloading is needed.

[lexjwa]

Thank you all for pointing to possible fix.

To load the multiple hosts from the database we are using vlucas/phpdotenv to connect to database and for some reason deployer was keeping database connection from project we have installed it in.

I am able to resolve the issue using createMutable instead of createImmutable method. Since we are interacting with multiple databases from the deploy.php we have to initiate the database connection each time we connect to a different database.

We can pass the .env file like this and overwrite existing environment variables.

$dotenv = Dotenv::createMutable(__DIR__, '.env');
$dotenv->safeLoad();
$dotenv->required(['DB_CONNECTION', 'DB_HOST', 'DB_PORT', 'DB_DATABASE', 'DB_USERNAME'])->notEmpty();
$capsule = new Capsule;
$capsule->addConnection([ // @Done: Getting these directly from project .env using vlucas/phpdotenv
    'driver'    => $_SERVER['DB_CONNECTION'],
    'host'      => $_SERVER['DB_HOST'],
    'port'      => $_SERVER['DB_PORT'],
    'database'  => $_SERVER['DB_DATABASE'],
    'username'  => $_SERVER['DB_USERNAME'],
    'password'  => $_SERVER['DB_PASSWORD'],
    'charset'   => 'utf8',
    'prefix'    => '',
]);
$capsule->setEventDispatcher(new Dispatcher(new Container));
$capsule->setAsGlobal(); // Optional: Make this Capsule instance available globally via static methods
$capsule->bootEloquent(); // Required when using setEventDispatcher(): Setup the Eloquent ORM

AND

$dotenv = Dotenv::createMutable(__DIR__, '/.build/release/.env');
$dotenv->load(); //Checks if .env file exists.
$dotenv->required(['DB_CONNECTION', 'DB_HOST', 'DB_PORT', 'DB_DATABASE', 'DB_USERNAME'])->notEmpty();
$capsule = new Capsule;
$capsule->addConnection([ // @Done: Getting these directly from project .env using vlucas/phpdotenv
    'driver'    => $_SERVER['DB_CONNECTION'],
    'host'      => $_SERVER['DB_HOST'],
    'port'      => $_SERVER['DB_PORT'],
    'database'  => $_SERVER['DB_DATABASE'],
    'username'  => $_SERVER['DB_USERNAME'],
    'password'  => $_SERVER['DB_PASSWORD'],
    'charset'   => 'utf8',
    'prefix'    => '',
]);
$capsule->setEventDispatcher(new Dispatcher(new Container));
$capsule->setAsGlobal(); // Optional: Make this Capsule instance available globally via static methods
$capsule->bootEloquent(); // Required when using setEventDispatcher(): Setup the Eloquent ORM
run('{{bin/php}} {{release_or_current_path}}/artisan migrate');
run('{{bin/php}} {{release_or_current_path}}/artisan db:seed');