Paw<\/a>!<\/p>\nHere’s how I set up the initial request in Paw:<\/p>\n
![\"Paw](\"https:\/\/www.padizio.com\/blog\/assets\/Screen-Shot-2017-03-04-at-11.57.48-AM.png\")
<\/p>\n
And here’s the code that Paw generated for PHP:<\/p>\n
<?php\n\n\/\/ Get cURL resource\n$ch = curl_init();\n\n\/\/ Set url\ncurl_setopt($ch, CURLOPT_URL, 'https:\/\/api.pushover.net\/1\/messages.json');\n\n\/\/ Set method\ncurl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'POST');\n\n\/\/ Set options\ncurl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);\n\n\/\/ Set headers\ncurl_setopt($ch, CURLOPT_HTTPHEADER, [\n \"Content-Type: application\/x-www-form-urlencoded; charset=utf-8\",\n ]\n);\n\/\/ Create body\n$body = [\n \"message\" => \"This is a test message\",\n \"title\" => \"Done\",\n \"token\" => \"your-app-token\",\n \"user\" => \"your-user-token\",\n ];\n$body = http_build_query($body);\n\n\/\/ Set body\ncurl_setopt($ch, CURLOPT_POST, 1);\ncurl_setopt($ch, CURLOPT_POSTFIELDS, $body);\n\n\/\/ Send the request & save response to $resp\n$resp = curl_exec($ch);\n\nif(!$resp) {\n die('Error: \"' . curl_error($ch) . '\" - Code: ' . curl_errno($ch));\n} else {\n echo \"Response HTTP Status Code : \" . curl_getinfo($ch, CURLINFO_HTTP_CODE);\n echo \"\\nResponse HTTP Body : \" . $resp;\n}\n\n\/\/ Close request to clear up some resources\ncurl_close($ch);\n<\/code><\/pre>\nAwesome. Now we’ve got a PHP script that can send a hard-coded message – assuming, of course, that you replace your-app-token<\/code> and your-user-token<\/code> with your relevant Pushover account details. Let’s adapt this into something we can run from the shell and pass arguments into.<\/p>\nFirst up, I’m going to paste the above into a file called finished<\/code>. For me, I put it in my ~\/bin<\/code> directory, because I’ve got that added to my $PATH<\/code> – meaning I’ll be able to run this script from anywhere. While I’m there, I’ll do a quick chmod +x<\/code> on it in the shell, so it becomes executable.<\/p>\nAt the top of my new finished<\/code> script, I’ll put the magic incantation that helps your shell know this is PHP:<\/p>\n#!\/usr\/bin\/env php\n<?php\n<\/code><\/pre>\nThat hash-bang line tells the shell to fire up the PHP interpreter. After that, the remaining PHP file gets executed automatically. Although, PHP being PHP, you still need the <?php<\/code> in order for the interpreter to, well, interpret. Otherwise it will just spit out your code back to you as plain text. Try it, it’s hilarious.<\/p>\nNow you’ll be able to run finished<\/code> on the command line and get your hard-coded message. Let’s take the arguments from the command line to turn that into the message. In a PHP shell script, $argv<\/code> will be automatically available as an array of all the arguments passed into the script – including, up front, the full path to the script itself. Here’s how we turn that into the $message<\/code> string at the top of the file:<\/p>\n$script_path = array_shift($argv); \/\/ This pops the script path off the front of the $argv array\n$message = implode(' ', $argv); \/\/ Concatenates the array together with spaces\n<\/code><\/pre>\nAnd then I modify the $body<\/code> array that Paw gave us:<\/p>\n...\n$body = [\n \"message\" => $message,\n...\n<\/code><\/pre>\nAnd that’s it! Now you can run:<\/p>\n
> some --long-running=task; finished The long running task finished\n<\/code><\/pre>\nSide note: I don’t call the script done<\/code> because unlike Casey, I use bash, and in bash done<\/code> is a control keyword – so bash just won’t run any script called done<\/code> unless I always give it the full path. Meh.<\/p>\n","protected":false},"excerpt":{"rendered":"A code post! How novel! Yesterday I was catching up on my blog reading and I ran across Casey Liss’ Shell \u2192 Watch Notifications. I love the idea – but it’s a bit of a kludge to put together as-is.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[30],"tags":[],"class_list":["post-666","post","type-post","status-publish","format-standard","hentry","category-code"],"_links":{"self":[{"href":"https:\/\/www.padizio.com\/blog\/wp-json\/wp\/v2\/posts\/666","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.padizio.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.padizio.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.padizio.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.padizio.com\/blog\/wp-json\/wp\/v2\/comments?post=666"}],"version-history":[{"count":13,"href":"https:\/\/www.padizio.com\/blog\/wp-json\/wp\/v2\/posts\/666\/revisions"}],"predecessor-version":[{"id":680,"href":"https:\/\/www.padizio.com\/blog\/wp-json\/wp\/v2\/posts\/666\/revisions\/680"}],"wp:attachment":[{"href":"https:\/\/www.padizio.com\/blog\/wp-json\/wp\/v2\/media?parent=666"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.padizio.com\/blog\/wp-json\/wp\/v2\/categories?post=666"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.padizio.com\/blog\/wp-json\/wp\/v2\/tags?post=666"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}