Build locally for production and remotely for staging

[jasperf]

We currently have the setup that we build locally and push to staging and production. I now want to use staging branch for staging and master for production. I would prefer only to push built files to production and not to staging.

So, it is possible to change my config to use npm run prod on staging and not on master or production?

<?php

namespace Deployer;

require 'recipe/laravel.php';
require 'vendor/deployer/recipes/recipe/cachetool.php';

// Configuration
set('repository', '[email protected]:user/app-v3.git');
set('default_stage', 'production');
set('git_tty', true); // [Optional] Allocate tty for git on first deployment
set('ssh_type', 'native');
set('cachetool', '/var/run/php/php7.4-fpm.sock');
set('keep_releases', 10);

// Make sure uploads & published , tls, logs aren't overwritten by deploying
set('shared_dirs', [
    'public/uploads',
    'public/published',
    'storage/logs',
    'storage/tls',
    'storage/app/public',
]);
set('shared_files', [
    '.env',
    '.transip_private_key',
]);
set('writable_dirs', [
    'public/uploads',
    'public/published',
    'storage/framework/cache/data',
    'storage/logs',
    'storage/tls',
    'storage/app/public',
]);

// SMART CUSTOM DEPLOY COMMANDS
task('db:migrate', function () {
    run('cd {{release_path}} && php artisan migrate --force');
});
task('horizon:terminate', function () {
    run('cd {{release_path}} && php artisan horizon:terminate');
});

task('queue:restart', function() {
    run('cd {{release_path}} && php artisan queue:restart');
});

task('reload:php-fpm', function () {
run('sudo /etc/init.d/php7.4-fpm restart'); // Using SysV Init scripts
});


// Hosts
// dep deploy production
// dep deploy staging

   host('staging')
   ->hostname('staging.app.com')
   ->user('forge')
   ->forwardAgent()
   ->stage('staging')
   // ->set('branch', 'staging') not in use yet
   ->set('deploy_path', '/home/forge/staging.app.com');

   host('production')
   ->hostname('app.com')
   ->user('forge')
   ->forwardAgent()
   ->stage('production')
   ->set('deploy_path', '/home/forge/app.com');

   host('prodold')
   ->hostname('prod-w-1.app.com')
   ->user('forge')
   ->forwardAgent()
   ->stage('prodold')
   ->set('deploy_path', '/home/forge/app.com');

// Run database migrations
after('deploy:symlink', 'db:migrate');

// Restart job
after('db:migrate', 'queue:restart');

// Clear OPCache
after('queue:restart', 'cachetool:clear:opcache');
after('cachetool:clear:opcache', 'horizon:terminate');

after('deploy', 'reload:php-fpm');
after('rollback', 'reload:php-fpm');

[jasperf]

At https://github.com/lorisleiva/laravel-deployer/blob/main/docs/how-to-npm.md which is a Laravel wrapper for PHP Deployer, they mention:

'hooks' => [
    'build' => [
        'npm:install',    // or yarn:install
        'npm:production', // or yarn:production
    ],
],

looking into this.. but not sure if this is wrapper native or Deployer native..

#2322 also mentioned Deployer 7 and currentHost but that is not stable yet nor are breaking changes quite clear yet.

[jasperf]

At #1719 I see

// Build assets
task('npm', 'npm ci; npm run prod')

Assume that works. Just need a conditonal to only run this for host staging host('staging') Did read at #1694 I could perhaps use onRoles()

Migration to Deployer 7

at Deployer Github repository there is a description on the migration from PHP Deployer 6 to 7 and changes needed I see now by the way. Not sure if currentHost would help though as I need to run npm only on staging. The method onRoles() will become select() I read.

Not quite sure why we would upgrade to Deployer 7 for our Laravel 8 app. Would require some changes and only willing to go for that if Deployer 7 is really a solid improvement. Will need to read more on that. For now onRoles would work for us in Deployer 6 just as well.