Migrating from Laravel-deployer want to keep the functionality of artisan command for CI/CD purposes

[isaiahfisher]

Currently, I am working on migrating from Laravel-deployer due to the author dropping support of the package. Our applications have a pretty complicated CI process that calls a deployer task via artisan:

php artisan deploy -s local_copy

Using the laravel-deployer the task was setup using the following strategy:

'local_copy' => [
            'hook:start',
            'deploy:prepare',
            'deploy:lock',
            'deploy:release',
            'upload',
            'deploy:shared',
            'deploy:vendors',
            'deploy:writable',
            'hook:ready',
            'deploy:symlink',
            'deploy:unlock',
            'cleanup',
            'hook:done',
        ]

And the config was all set in localhost:

'deploy_path' => '/var/www',
'user' => 'www-data'

Is there a way to maintain this functionality directly with deployer to continue enabling our CI/CD process?

[isaiahfisher]

Alternatively, is there a way to just change it from running as an artisan command to running the commands locally during the deployment? something like that same strategy but using dep deploy and still running it locally?

[isaiahfisher]

It looks like I can run this locally by using localhost()->set('deploy_path', '/var/www')->set('remote_user', 'www-data');

Then in my gitlab ci I had to replace the php artisan deploy -s local_copy with vendor/deployer/deployer/dep deploy.

This successfully runs the laravel recipe.