+ 
+* Allows packages to register new commands
+
+Note:
+
+* Artisan is the command line interface for Laravel
+ * Built on top of Symfony Console (more in a minute)
+* Easily scaffold models, controllers, console commands, and more!
+* Third-party packages can register new commands
+
+----
+
+### Joomlatools Console
+
+* CLI framework for Joomla
+* Manage sites, extensions, databases, etc.
+ * Includes virtual host management
+
+Note:
+
+* Joomla counterpart of WP-CLI or Drush
+* Similar kinds of features: managing sites, users, extensions, etc.
+ * Kind of neat: has the "vhost" command for managing Apache + nginx virtual hosts
+
+---
+
+## CLI Concepts
+
+Note:
+
+While it's not any more difficult than building anything else in PHP, there are some concepts that you need to understand if you're going to build for the CLI
+
+----
+
+### Composability
+
+Good CLI commands should be **composable!**
+
+Note:
+
+Composability is one of the major tenents of *nix operating systems.
+
+Who can tell me what this means?
+
+----
+
+### Rule of Composability
+
+> Developers should write programs that can communicate easily with other programs. This rule aims to allow developers to break down projects into small, simple programs rather than overly complex monolithic programs.
+
+Eric S. Raymond, [*The Art of Unix Programming*](https://en.wikipedia.org/wiki/The_Art_of_Unix_Programming)
+
+Note:
+
+Small programs that can communicate with each other through common interfaces (data streams) and be combined to do most anything
+
+----
+
+### Data Streams
+
+Three default data streams:
+
+0. STDIN - input
+1. STDOUT - output
+2. STDERR - errors
+
+Note:
+
+Think of a data stream as a channel that can be read from and/or written to.
+
+Generally, there are three data streams to concern yourself with:
+
+1. STDIN represents the data coming into your command
+2. STDOUT is where you're sending data out
+3. STDERR is where we collect any error information
+
+Streams can be redirected (e.g. write errors to a log file, send the output of one command as the input into another)
+
+----
+
+### Data Streams in Practice
+
+```cli [|2-3|4|5|6|7]
+# Get the number of unique IP addresses in access.log
+$ grep -Eo "([0-9]{1,3}[\.]){3}[0-9]{1,3}" \
+ /var/log/nginx/access.log \
+ | uniq \
+ | wc -l \
+ | xargs printf "%d unique IP addresses detected"
+43282 unique IP addresses detected
+```
+
+
+Note:
+
+Counting the number of IP addresses in access.log:
+
+1. Use `grep` to match anything that looks like an IP, returning only that part
+ * STDOUT would be a series of IP addresses, one per line
+2. Pipe that list of addresses into `uniq` to remove duplicates
+ * STDOUT from grep became STDIN to uniq
+3. Pipe the filtered list into `wc` (word count) with the `-l` option (count the number of lines)
+ * STDOUT becomes an integer representing the number of lines
+4. Use `xargs` to append that number to printf to give a summary
+
+Five commands (grep, uniq, wc, xargs, and printf), each playing their part
+
+----
+
+### Exit Codes
+
+Exit codes tell us how everything went:
+
+| Code | Meaning |
+| --- | --- |
+| 0 | All good! |
+| 1 | Generic error |
+| 2 | Incorrect command/arg usage |
+| 3–255 | Specific errors |
+
+Note:
+
+When a command exits, we do so with an exit code.
+
+* 0 means that no errors occurred
+* 1–255 represent some sort of error
+ * 1 is generally a catch-all for errors
+ * 2 is typically meant to indicate incorrect command/arg usage
+ * 3–255 may have special meaning; there are a few conventions in the 120s for permissions errors
+* You might use 3 for filesystem issues, 4 for network connectivity issues, etc.
+
+Most scripts you come across will generally use 0 or 1: did it succeed or fail (respectively)?
+
+----
+
+### Exit Codes & Boolean Operators
+
+```cli [1-2|4-5|7-8|10-11]
+# Celebrate a non-zero exit code!
+$ do-something && celebrate
+
+# Hang your head in shame if something fails
+$ do-something || hang-head-in-shame
+
+# Put the operators together
+$ (do-something && celebrate) || hang-head-in-shame
+
+# Semi-colons don't care, they just separate commands
+$ do-something; celebrate; hang-head-in-shame
+```
+
+
+Note:
+
+We can chain operations based on the exit code of the previous command:
+
+* Double-ampersand ("and") will proceed if the previous operation had an exit code of zero
+* Double pipes ("or") will proceed if we encountered a non-zero exit code
+* Both can be used, but use parentheses if you want the "or" to be tied to the "and" sequence
+* Semi-colons can chain multiple commands with no attention paid to exit codes
+
+----
+
+### Arguments + Options
+
+```cli [1-3|5-8|10-12]
+# Arguments
+$ cd /var/www
+$ grep "Some text" file.txt
+
+# Options
+$ git commit -m "This is my commit message"
+$ ls -a -l
+$ ls -al
+
+# Long options
+$ composer outdated --format=json
+$ git push --force-with-lease
+```
+
+
+Note:
+
+* Arguments: positional parameters, passed in order
+* Options: Can optionally have values, single dash + single letter. Can usually be combined
+ * e.g. `ls -a -l` is the same as `ls -al`
+* Long options: Same as regular options, but with two dashes + multiple letters
+ * Often easier to read or decode at a glance
+
+----
+
+### Conventions for Options
+
+```plaintext
+OPTIONS:
+
+ -h|--help Print usage instructions
+ -q|--quiet Silence all output
+ -v|--version Print version information
+ --verbose Print additional output
+```
+
+Note:
+
+While these aren't mandatory, there are a few common patterns you'll come across:
+
+* Many scripts will reserve `-h` and/or `--help` for displaying usage instructions
+* `-q` or `--quiet` is generally used to silence output
+ * Especially useful for commands that may be run on a cron job, where you only want output if something goes wrong
+* `-v` has two common uses: either as a short-hand for version or verbose (print additional information)
+
+Notice that most of these options have both short and long versions!
+
+----
+
+### Environment Variables
+
+Set and read variables in the current environment
+
+```cli [1-2|4-5|7-8|]
+# Export from shell files
+export CURRENT_CITY="Bowling Green"
+
+# Set directly in shell
+$ CURRENT_CITY="Chicago"
+
+# Set as you call a command
+$ CURRENT_CITY="Rosemont" some-script
+```
+
+
+Note:
+
+There are three ways to set environment variables:
+
+1. Export them from within a file like `.bash_profile`, which is sourced as your start your shell
+ * Persists for all sessions
+2. Explicitly set the variable in the shell
+ * Persists for remainder of session
+3. Set them as you're calling a command
+ * Only set for the single command invocation
+
+If I set it all three of these ways, what would some-script get for the value of CURRENT_CITY? (Rosemont)
+
+----
+
+### Environment Variables in PHP
+
+```php [1-2|4-5|7-8|10-11]
+# Get array of all environment variables
+getenv();
+
+# Retrieve a specific variable (false if unset)
+getenv('SOMEVAR');
+
+# Set an environment variable
+putenv('SOMEVAR=some_value');
+
+# Delete an environment variable
+putenv('SOMEVAR=');
+```
+
+
+Note:
+
+There are two primary functions for working with environment variables in PHP:
+
+1. `getenv()` reads from the environment variables
+2. `putenv()` writes to the environment variables
+
+There's also the `$_ENV` superglobal, but writing to this array has no impact on the environment.
+
+----
+
+### The cli SAPI
+
+Additional **S**erver **API** for PHP
+
+```php
+// Check the current SAPI. We can also use PHP_SAPI here.
+if (php_sapi_name() === 'cli') {
+ // We're on the command line!!
+}
+```
+
+Note:
+
+* PHP has a number of server APIs that can introduce alternate functionality; cli is one of them
+* Other SAPIs include apache, cgi-fcgi, fpm-fcgi, litespeed, phpdbg, etc.
+* We can determine what SAPI we're using with the `php_sapi_name()` function or `PHP_SAPI` constant.
+
+----
+
+### Special CLI globals
+
+int $argcarray $argv
+ chmod(), mkdir(), etc.
+ exec()shell_exec()system()passthru()escapeshellcmd()escapeshellarg()How high should I count? [10]: 5Shall I shout it? [y/N]y1!
-2!
-3!
-4!
-5!
diff --git a/slides/php-cli-tools.md b/slides/php-cli-tools.md
deleted file mode 100644
index c159738..0000000
--- a/slides/php-cli-tools.md
+++ /dev/null
@@ -1,14 +0,0 @@
-### [PHP-CLI Tools](https://github.com/wp-cli/php-cli-tools)
-
-* Simplify input + output
- - Tabular + tree displays
- - Progress indicators
-* Maintained by the WP-CLI team
-
-Note:
-
-* Library that simplifies input + output
- - Prompts, menus, arguments
- - Output formatting
- - Tabular + tree displays
- - Progress indicators
diff --git a/slides/php-sapi.md b/slides/php-sapi.md
deleted file mode 100644
index 6be76b0..0000000
--- a/slides/php-sapi.md
+++ /dev/null
@@ -1,13 +0,0 @@
-### Know the current Server API
-
-```php
-// Make sure this script is being run over the PHP CLI!
-if ('cli' !== php_sapi_name()) {
- return;
-}
-```
-
-Note:
-
-* Used to running in something like the fpm-fcgi SAPI for web requests.
-* Use the php_sapi_name() function or PHP_SAPI constant to determine the server API being used
diff --git a/slides/spidey-sense.md b/slides/spidey-sense.md
deleted file mode 100644
index e9acf61..0000000
--- a/slides/spidey-sense.md
+++ /dev/null
@@ -1,5 +0,0 @@
-
-
-Note:
-
-If the thought of executing arbitrary system commands sets off your security sense, you're 100% correct.
diff --git a/slides/symfony-console.md b/slides/symfony-console.md
deleted file mode 100644
index aa367dd..0000000
--- a/slides/symfony-console.md
+++ /dev/null
@@ -1,12 +0,0 @@
-### [Symfony Console Component](http://symfony.com/doc/current/components/console/index.html)
-
-* CLI framework of choice
-* Handlers for input & output
-* Born to be tested
-
-Note:
-
-* De facto tool for writing PHP CLI scripts
-* Ships with methods for all sorts of input and output handling
-* Designed from the ground-up to be easily tested
-* Easily integrates with other Symfony components
diff --git a/slides/system-commands.md b/slides/system-commands.md
deleted file mode 100644
index c61716a..0000000
--- a/slides/system-commands.md
+++ /dev/null
@@ -1,9 +0,0 @@
-### System commands
-
-* PHP can natively do a lot of common Unix operations: [`copy`](http://us3.php.net/manual/en/function.copy.php), [`chmod`](http://us3.php.net/manual/en/function.chmod.php), [`chown`](http://us3.php.net/manual/en/function.chown.php), etc.
-* Can also execute arbitrary system operations!
-
-Note:
-
-* PHP has functions to do a lot of common operations, but can also execute arbitrary system commands
- - Can be both extremely helpful and extremely...dangerous.
diff --git a/slides/system-commands2.md b/slides/system-commands2.md
deleted file mode 100644
index 47df1a2..0000000
--- a/slides/system-commands2.md
+++ /dev/null
@@ -1,16 +0,0 @@
-#### Executing System Commands
-
-exec()shell_exec()\`ls -al` === shell_exec('ls -al')system()passthru()