These are chat archives for shipitjs/shipit

25th
Jan 2015
Tim Kelty
@timkelty
Jan 25 2015 22:23
Howdy
Greg Bergé
@neoziro
Jan 25 2015 22:24
@timkelty leave the other room please
Tim Kelty
@timkelty
Jan 25 2015 22:24
Done
Greg Bergé
@neoziro
Jan 25 2015 22:25
@timkelty thanks
Tim Kelty
@timkelty
Jan 25 2015 22:25
yep. Really liking this project, thanks for the work!
Just what we were looking for
Greg Bergé
@neoziro
Jan 25 2015 22:26
Nice! I love it too, it's very simple and powerful, I use it on all of my projects and it's used by Ghost and Le Monde.
Tim Kelty
@timkelty
Jan 25 2015 22:27
We can't wait to switch over - we've been dreading upgrading all our Cap scripts to 3
Esp since we hardly do ruby any more
Did you see my question in the other room about doing a reverse Shipit.prototype.remoteCopy?
Greg Bergé
@neoziro
Jan 25 2015 22:28
yes
maybe we can add a options to reverse the copy
Tim Kelty
@timkelty
Jan 25 2015 22:28
ah lovely
yeah that could be nice
Greg Bergé
@neoziro
Jan 25 2015 22:29
do we just have to reverse src and dest?
Tim Kelty
@timkelty
Jan 25 2015 22:30
well it seems to always attach the ssh protocols to the dest (2nd arg)
Greg Bergé
@neoziro
Jan 25 2015 22:31
ok, can you make a PR?
Tim Kelty
@timkelty
Jan 25 2015 22:31
will do
My other question was dealing with paths that aren't config options (e.g. shipit.currentPath)
Suppose I'm writing a task that needs shipit.currentPath, but need it independent of the deploy task
Greg Bergé
@neoziro
Jan 25 2015 22:31
they are added during the deployment flow
Tim Kelty
@timkelty
Jan 25 2015 22:31
right
so do I just need to create it every time? shipit.currentPath = path.join(shipit.config.deployTo, 'current');
Looks like that's what you're doing in deploy/rollback
Greg Bergé
@neoziro
Jan 25 2015 22:33
Hmm yes for now, but I will probably change that in future
but it's a lot of changes right now
so I will wait
Tim Kelty
@timkelty
Jan 25 2015 22:34
I'll just do it like that for now