shipit
shipit copied to clipboard
Universal automation and deployment tool ⛵️
I have an issue where I have a task to run database migrations via knex that is failing, but shipit just keeps running and never triggers the catch block. ```...
Pretty "newbie" simple configuration: ```javascript module.exports = shipit => { require('shipit-deploy')(shipit) shipit.initConfig({ default: { deployTo: '~/tmp/super-project', repositoryUrl: '[email protected]:gremo/webpack-boilerplate.git', }, staging: { servers: '[email protected]', }, }); shipit.task('pwd', () => shipit.remote('cd ~/httpdocs...
The suggested solution is this: ```javascript shipit.blTask('app:build', async () => { await shipit.remote(`cd ${shipit.releasePath} && yarn install && yarn build`); }); shipit.on('updated', () => { shipit.start('app:build'); }); ``` But how...
After update to version 5.2.0 or higher I can't make deploy cause the process break on tar comand: `Running "mkdir -p ~/folder/releases/20200324175447" on host "ip".` `Running "cd ~/folder/releases/20200324175447 && &&...
Ssh-pool has the tar+scp fallback if rsync is not present ... but it checks the rsync presence only in the local machine. Rsync needs to be available on both ends...
Hi, I recently take over a project that use shipit for its own deploy and I never used. The following versions are in use ``` "shipit-cli": "4.2.0", "shipit-deploy": "4.1.4", "shipit-npm":...
Implement a new command `shipit --init` that will generate an empty shipitfile: ```js module.exports = shipit => { shipit.initConfig({ default: {}, production: { servers: '[email protected]', }, }) shipit.task('hello', () =>...
it looks like that since upgrading shipit-cli from 3.0.0 to 4.1.0 and shipit-deploy from 2.5.1 to 4.1.0, the rsync command broke my deploy script with this error: ``` @tools.bsmart.so-err Warning:...
Could it just ignore the previous releases if they don't exist? This is the error that occurs: ``` Error: Command failed: ssh -i /home/user/.ssh/id_rsa [email protected] "cp -a /var/www/project/releases/20180829065949/. /var/www/project/releases/20180829113223" cp:...
Been banging my head against the wall trying to figure out why I can't get this working. I'm convinced this must be a bug with how `ssh-pool` is opening connections...