fix: update DB env vars during initialization

[artengin]

Refs: #42

[coveralls]

Pull Request Test Coverage Report for Build 18334096819

Details

• 21 of 21 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.06%) to 97.973%

---

Totals
Change from base Build 18301590721:	0.06%
Covered Lines:	290
Relevant Lines:	296

---

💛 - Coveralls

[Copilot]

Pull Request Overview

This PR fixes database environment variable configuration during the initialization process by replacing direct Artisan calls with shell_exec commands to ensure proper environment setup for migrations.

• Replaces Artisan::call('migrate') with a new runMigrations() method that configures database environment variables before running migrations via shell_exec
• Changes Artisan::call('vendor:publish') to shell_exec in the publishWebLogin() method for consistency
• Updates test expectations to include the new shell_exec calls and removes the assertWebLoginPublished() method calls from test assertions

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
src/Commands/InitCommand.php	Adds database configuration setup in new runMigrations() method and switches to shell_exec for vendor:publish command
tests/InitCommandTest.php	Updates test expectations to match new shell_exec approach and removes web login assertions
tests/TestCase.php	Removes unused assertFileEqualsFixture() method

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Using shell_exec without error handling could mask migration failures. Consider checking the return value or using a more robust command execution method that can capture and handle errors.

Suggested change

	shell_exec("php artisan migrate");
	$output = [];
	$exitCode = 0;
	exec("php artisan migrate", $output, $exitCode);
	if ($exitCode !== 0) {
	$this->error("Migration failed with exit code {$exitCode}.\nOutput:\n" . implode("\n", $output));
	throw new \RuntimeException("Migration failed. See error output above.");
	}

[DenTray]

@artengin I not sure, could you please check it?

[artengin]

This method works,
but the shell command also outputs error messages from the migrations.

[artengin]

exec() :

shell_exec:

$output = shell_exec('php artisan migrate --ansi 2>&1');
echo $output;

[DenTray]

@artengin I not sure, could you please check it?

[artengin]

The following errors:

PHP Fatal error: Declaration of Monolog\Logger::emergency(Stringable|string $message, array $context = []): void must be compatible with Psr\Log\LoggerInterface::emergency($message, array $context = []) in /var/www/test/test-laravel/vendor/monolog/monolog/src/Monolog/Logger.php on line 683
PHP Fatal error: Uncaught Error: Class "Monolog\Logger" not found in /var/www/test/test-laravel/vendor/monolog/monolog/src/Monolog/Handler/AbstractHandler.php:60

did not occur because of our package, but due to an internal issue in Laravel.

Reference to the related issue in laravel/framefork #57295

As a result,, using --no-scripts is no longer necessary, because it was causing other problems for us.

[artengin]

Tested on the laravel-empty-project — everything works.

[artengin]

If we add an echo to all the commands to display a message about the execution result, it will look like this: