Custom CLIs with AHOY

Add new commands? Create specific commands per project? Reuse those commands in others and even in scripts for CircleCI or ProboCI builds? Of course it is possible! And the best is that you can do it no matter the technology you use, but... how? Well, you just need a little AHOY.

AHOY (https://github.com/ahoy-cli/ahoy) is an open source tool that allows you to automate workflows, basically what it does is to create aliases and run commands locally, through containers or even over ssh. In this session we are going to talk about: 

• how to create our own CLIs for a Drupal project, 
• how to use AHOY, 
• why we should do it, and 
• which benefits do we get from it.

In this talk I will explain how AHOY helps to improve a dev team workflow and we will see an use case in which we use it for development with a drupal 7 distribution.

Why should you come?

Well, I think it is very useful that everyone in a team use the same set of commands, it helps a lot when it comes to replicate a bug and troubleshoot it; also, those commands created are easy to use and are self-documented, which makes easier for the people to get into it. So, you're invited to come, lets learn together!

Who I am?

My name is Dharizza Espinach Barahona (Twitter, Github, drupal.org), I come from Costa Rica and work as Drupal Backend Developer for a costarican company called Estudio Manatí http://estudiomanati.com/
I've been working with Drupal for two years now and I've just started in the devops world. I've talked in the Drupal Camp Chile 2015 (http://camp.drupalchile.org/es) about drupal migrations basics and I went to the BADCamp 2016 (https://2016.badcamp.net/) and talked about behat in the devops summit.