These are chat archives for shipitjs/shipit

15th
Jul 2015
Naveen Singh
@w0w
Jul 15 2015 03:08
using shipit-shared to copy shared files over releases
      shared: {
        overwrite: true,
        dirs: [
          'keys'
        ],
        files: [
          {
            path: 'server/config.production.json',
            overwrite: false,
            chmod: '755',
          },
          'server/datasources.production.json'
          ]
    }
when i run shipit production shared:create-dirs
it creates directory for files as well

Running 'shared:create-dirs' task...
Running "if [ -h /opt/core-api/current ]; then readlink /opt/core-api/current; fi" on host "54.169.80.255".
@54.169.80.255 releases/20150715025915
Creating shared directories on remote.
Running "mkdir -p /opt/core-api/shared/keys" on host "54.169.80.255".
Running "mkdir -p /opt/core-api/shared/server/config.production.json" on host "54.169.80.255".
Running "mkdir -p $(dirname /opt/core-api/shared/server/datasources.production.json)" on host "54.169.80.255".
Tim Kelty
@timkelty
Jul 15 2015 09:52
@w0w verified. Just pushed out 4.1.1 to fix that: https://github.com/timkelty/shipit-shared/tree/4.1.1
Currently working on tests to prevent these kind of bugs :)
Naveen Singh
@w0w
Jul 15 2015 11:40
@timkelty thanks
Naveen Singh
@w0w
Jul 15 2015 12:11
@timkelty one more interesting thing i observed was, when the files are not in shared folder it creates a directory by the name of file
Tim Kelty
@timkelty
Jul 15 2015 15:34
@w0w creates it in the shared folder?
If you want to make a GH issue I'll get to to later on today
Naveen Singh
@w0w
Jul 15 2015 18:20
@timkelty yes in the shared folder, but it works for now