<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cli on Aaron West's technology blog</title><link>https://www.aaronwest.net/tags/cli/</link><description>Recent content in Cli on Aaron West's technology blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 30 Jul 2015 10:46:00 -0500</lastBuildDate><atom:link href="https://www.aaronwest.net/tags/cli/index.xml" rel="self" type="application/rss+xml"/><item><title>Exporting and Importing GitHub Labels</title><link>https://www.aaronwest.net/blog/exporting-and-importing-github-labels/</link><pubDate>Thu, 30 Jul 2015 10:46:00 -0500</pubDate><guid>https://www.aaronwest.net/blog/exporting-and-importing-github-labels/</guid><description>&lt;p&gt;At work we&amp;rsquo;re in the process of migrating all of our code repositories from &lt;a href="https://bitbucket.org/"&gt;Bitbucket&lt;/a&gt; to &lt;a href="https://github.com"&gt;GitHub&lt;/a&gt;. Our main driver for this change, and something I should probably write about here, is integrating all of our project management and process orchestration in one tool. This brings our issue management, project planning, state visualization, and more into the tool we use to manage code.&lt;/p&gt;
&lt;p&gt;A large part of the migration process is moving our individual repos and getting them set up like they were on Bitbucket. One of these tasks is configuring GitHub Labels in each repo/project. We have a documented and standardized set of labels and I began the process by manually adding each label into the first repo. Then I did the same thing for a second repo. It&amp;rsquo;s fairly tedious work so I looked around to see if you could export/import labels in GitHub.&lt;/p&gt;</description></item><item><title>How to Background Linux Console Processes</title><link>https://www.aaronwest.net/blog/how-to-background-linux-console-processes/</link><pubDate>Sun, 26 Jul 2015 13:30:00 -0500</pubDate><guid>https://www.aaronwest.net/blog/how-to-background-linux-console-processes/</guid><description>&lt;p&gt;This week our data team were talking about ways to run a Python script without having the execution attached to your console session. There&amp;rsquo;s more than way one to accomplish this but here&amp;rsquo;s the one they settled on.&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;nohup python python_script.py &amp;lt;/dev/null &amp;amp;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The discussion reminded me of a similar, and equally useful, workflow we had a Dataium. We used all kinds of databases over the years but in the beginning MySQL 5.5.x was our goto. We operated a fairly sizable database which served as a backend to a desktop Adobe AIR / Flex application. One of the challenges we had with the configuration was performance following a database restart. We approached this problem by writing SQL scripts which mirrored common query patterns from our users. This concept of &lt;em&gt;warming the MySQL query cache&lt;/em&gt; was incredibly useful.&lt;/p&gt;</description></item><item><title>How to Retrieve Your Wi-Fi Password on Mac</title><link>https://www.aaronwest.net/blog/how-to-retrieve-your-wi-fi-password-on-mac/</link><pubDate>Thu, 23 Jul 2015 08:00:00 -0500</pubDate><guid>https://www.aaronwest.net/blog/how-to-retrieve-your-wi-fi-password-on-mac/</guid><description>&lt;p&gt;I don&amp;rsquo;t generally forget the password for Wi-Fi networks I use, mainly because I use &lt;a href="http://www.1password.com"&gt;1Password&lt;/a&gt; to store all secrets. But, I ran across the ability to retrieve the password, in plain text, from the OS X Keychain of an SSID I&amp;rsquo;ve previously connected with. Not a huge amount of utility to this but it&amp;rsquo;s interesting the capability exists.&lt;/p&gt;
&lt;p&gt;In the command below I read the the keychain and hone-in on just the password portion. Replace &lt;code&gt;&amp;lt;SSID_NAME&amp;gt;&lt;/code&gt; with the name of of a valid SSID you&amp;rsquo;ve connected with in the past. Keep in mind case sensitivity matters. You can leave off &lt;code&gt;| grep password&lt;/code&gt; and retrieve the whole item too. This command requires authentication so you&amp;rsquo;ll be asked to enter your username and password.&lt;/p&gt;</description></item><item><title>Flushing DNS Cache on Mac OS X</title><link>https://www.aaronwest.net/blog/flushing-dns-cache-on-mac-os-x/</link><pubDate>Mon, 20 Jul 2015 16:43:00 -0500</pubDate><guid>https://www.aaronwest.net/blog/flushing-dns-cache-on-mac-os-x/</guid><description>&lt;p&gt;Below are the various Bash commands needed to flush DNS on Mac OS X. There are several different versions of the commands depending on which version of OS X in use. Ensure you are selecting the command appropriate for your OS. HT to &lt;a href="http://osxdaily.com/2014/11/20/flush-dns-cache-mac-os-x/"&gt;OSXDaily&lt;/a&gt; for additional explanations on what is happening under the covers.&lt;/p&gt;
&lt;h4 id="flush-dns-on-os-x-yosemite-10104-and-newer"&gt;Flush DNS on OS X Yosemite 10.10.4 and Newer&lt;/h4&gt;
&lt;p&gt;When 10.11.x aka &amp;lsquo;El Capitan&amp;rsquo; ships this command should continue to function. This set of commands will flush all DNS caches on OS X including Multicast DNS and Unicast DNS.&lt;/p&gt;</description></item><item><title>Generating SSH Keys on Mac OS X</title><link>https://www.aaronwest.net/blog/generating-ssh-keys-on-mac-os-x/</link><pubDate>Sun, 19 Jul 2015 16:41:00 -0500</pubDate><guid>https://www.aaronwest.net/blog/generating-ssh-keys-on-mac-os-x/</guid><description>&lt;p&gt;Generating an SSH key without a password. For example, for passphraseless old school Hadoop clusters. This is generally done from within a users home directory such as /Users/username on Mac.&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;ssh-keygen -t rsa -P &lt;span style="color:#e6db74"&gt;&amp;#34;&amp;#34;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Generating an SSH key with a password. This is generally done from within a users home directory such as /User/username on Mac.&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;ssh-keygen -t rsa
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;How to copy a generated SSH key to the Mac clipboard. This is arguably better than manually copying and pasting.&lt;/p&gt;</description></item></channel></rss>