<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by A. Tate Barber on Medium]]></title>
        <description><![CDATA[Stories by A. Tate Barber on Medium]]></description>
        <link>https://medium.com/@tatemz?source=rss-87150537fd29------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*L-XHCjFVDA1DVgnJ-lUBXg.jpeg</url>
            <title>Stories by A. Tate Barber on Medium</title>
            <link>https://medium.com/@tatemz?source=rss-87150537fd29------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 14:49:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tatemz/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[My Time at WordCamp Sacramento]]></title>
            <link>https://medium.com/@tatemz/my-time-at-wordcamp-sacramento-490202b587a5?source=rss-87150537fd29------2</link>
            <guid isPermaLink="false">https://medium.com/p/490202b587a5</guid>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[wordcamp]]></category>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[kindness]]></category>
            <dc:creator><![CDATA[A. Tate Barber]]></dc:creator>
            <pubDate>Mon, 24 Oct 2016 03:57:04 GMT</pubDate>
            <atom:updated>2016-10-24T03:57:04.129Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6cMCewx7b2IlIhjGJqC6Gw.jpeg" /></figure><p>I have attended many tech conferences in the past years. Many of them I attend in order to gather information on new technology, learn new skills, as well as network. This past weekend, I attended WordCamp Sacramento and had one of the best conference experiences I have had in a long time.</p><p>I was super pumped to be attending the conference as I had always wanted to see what other WordCamps were like! I flew into Sacramento from Northwest Arkansas, used Uber for the first time, and ended up having my spirits crushed when my driver made a comment about how my hotel was in a bad part of town — he was right. The area was <a href="http://www.sacbee.com/opinion/opn-columns-blogs/erika-d-smith/article74324927.html">scattered with prostitution</a>, the group next to my room played loud music until 2:00am, my room smelled awful, and I opted to sleep on top of one of the bath towels rather than use the sheets. Obviously, I did what homework I could, but the internet reviews and photos failed me. Thankfully, I was tired enough to sleep through my discomfort.</p><p>The next morning, I ubered to the WordCamp venue at California State University in Sacramento. I was immediately greeted by friendly WordCamp volunteers and all of my fears of being a loner for the weekend were immediately dissolved.</p><blockquote>This past weekend, I attended WordCamp Sacramento and had one of the best conference experiences I have had in a long time.</blockquote><p>The first few sessions were great, and I was feeling highly motivated. For my talk, I decided to start the first few moments with my thoughts on this motivation and how the WordPress community is such a huge inspiration for people who are passionate about doing what they love. What I thought was a simple rant turned out to have a deep impact on the people there. Afterwards, people were coming to me offering much encouragement and thankfulness — I felt humbled alongside a boost of my ego :-)</p><p>After a first day of great sessions, the dessert party was a blast! I had a chance to talk with many people and learn about their careers, their passions, and their lives — everyone was kind and cheerful. I loved this part of the evening as it seemed I could just sit down with anybody and feel as if we had been good friends for years.</p><p>Earlier that afternoon, I tweeted asking if anyone had a couch I could surf on so I could avoid the shady hotel.</p><h3>Tate Barber on Twitter</h3><p>😅... The internet failed me and I have a hotel in a bad part of town - not very fun. Anyone at #wcsac have a couch I can surf on? 😬</p><p>That night, me and a few others, who also came from out of town, went out for dinner and drinks — it was great conversation! Jeff, one of the guys at dinner, had a spare couch and was kind enough to let me crash.</p><p>This level of charitable kindness is not often found, especially at tech conferences where everyone is usually concerned about networking and ego boosting. At WordCamps, though, the “spirit of open source” means much more than open source code contribution, sharing of skills, or the sharing of knowledge — it also encompasses the sharing of kindness, friendship, and heartfelt support. Just ask any person who has been to a WordCamp or a WordPress meetup and you will know!</p><blockquote>I was immediately greeted by friendly WordCamp volunteers and all of my fears of being a loner for the weekend were immediately dissolved.</blockquote><p>The people from this weekend were some of the kindest people I had ever met. When I prepared to uber back to the airport, Jennifer, one of the organizers of WordCamp Sacramento gave me a big hug along with a kind “Thank you”. If the music had been just right, I might have teared up because the kindness was really pulling on my heart strings — I had kind of expected to be a sort of out-of-town loner for most of the weekend.</p><h3>WordCamp Sacramento on Twitter</h3><p>HUGE THANK YOUS to all #WordCamp #Sacramento organizers &amp;amp; volunteers (not all pictured) 👏👏👏 #wcsac</p><p>Needless to say, thank you to all you guys from WordCamp Sacramento! You are all great people and only I hope I can attend next year, but saying hello via Twitter will have to suffice until then.</p><blockquote>At WordCamps, though, the “spirit of open source” means much more than open source code contribution, sharing of skills, or the sharing of knowledge — it also encompasses the sharing of kindness, friendship, and heartfelt support.</blockquote><p>Your friend,<br>Tate</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=490202b587a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I Love Docker: A Use Case in Minecraft]]></title>
            <link>https://medium.com/@tatemz/why-i-love-docker-a-use-case-in-minecraft-b9f2a519d3ce?source=rss-87150537fd29------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9f2a519d3ce</guid>
            <category><![CDATA[videogames]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[minecraft]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[A. Tate Barber]]></dc:creator>
            <pubDate>Thu, 11 Aug 2016 03:48:54 GMT</pubDate>
            <atom:updated>2016-08-11T16:14:32.467Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/855/1*7p-GXoHdrnj-Tjvtqpbomw.png" /><figcaption><a href="https://www.reddit.com/r/Minecraft/comments/jjnho/so_i_uh_built_a_whalehouse/">https://www.reddit.com/r/Minecraft/comments/jjnho/so_i_uh_built_a_whalehouse/</a></figcaption></figure><p>Most Tuesdays, my friend, Daniel runs a <a href="http://twitch.tv/afteracts">Twitch stream</a> where he plays some video games — I tend to tag along. We have had a <a href="https://www.youtube.com/watch?v=CnQyiLE2iag&amp;list=PLDxiKWkdfHIyXV7rIFohP3TTcXCnBn09x">casual Minecraft live series</a> for a few months in which we play a regular vanilla survival map. We have been using <a href="https://minecraft.net/en/realms/">Minecraft Realms</a> as it is a no-hassle way to have a persistent co-op server. However, the other day, we decided we wanted to do a content series using Minecraft’s “hardcore” setting which prevents you from respawning after you die. For some reason, hardcore mode is <a href="https://help.mojang.com/customer/en/portal/articles/1666365-creating-your-realm">not available on Minecraft Realms</a>. Additionally, hardcore mode is not available when opening your local client to the LAN network.</p><p>Thus, we needed to create our own server. Being a developer, I have a well-used account with <a href="https://m.do.co/c/e9fc51b8556f">Digital Ocean</a> and thus, would usually just spin up a bare Ubuntu machine and install and configure Minecraft myself <a href="https://www.digitalocean.com/community/tutorials/how-to-set-up-a-minecraft-server-on-linux">via command line</a>. However, Docker has been my forte these days…</p><p>Thankfully, <a href="https://kitematic.com/">Kitematic</a> has an <a href="https://github.com/kitematic/minecraft/">out-of-the-box Minecraft image</a>. My friend Daniel was about to cancel the Minecraft session since we didn’t have time to configure our own server, but I told him to give me a moment…</p><iframe src="https://cdn.embedly.com/widgets/media.html?url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DMsqzqzRp-4w&amp;src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FMsqzqzRp-4w%3Ffeature%3Doembed&amp;type=text%2Fhtml&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/759578cfd15a5a1c4a41277ca280dc44/href">https://medium.com/media/759578cfd15a5a1c4a41277ca280dc44/href</a></iframe><p>This is precisely why I love Docker: it makes it so easy to use community created resources to start and run services without installing them on your computer. Instead, they only exist within easily disposable containers. On top of that, it usually takes only one to two commands to have something up and running.</p><p>Since I needed to edit the Minecraft server’s settings in this example, I built my own image that can handle configurable settings.</p><h3>Tate Barber on Twitter</h3><p>In case you want to run your @Minecraft server via @docker use my @kitematic based image with conf varshttps://github.com/tatemz/docker-minecraft ...</p><p>If you are not savvy with command line, thankfully, Kitematic has a nice GUI…</p><iframe src="https://cdn.embedly.com/widgets/media.html?url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DnB2uulZvvM0&amp;src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FnB2uulZvvM0%3Ffeature%3Doembed&amp;type=text%2Fhtml&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6988d53aa430a13eff7e8fdf2dad3142/href">https://medium.com/media/6988d53aa430a13eff7e8fdf2dad3142/href</a></iframe><p>So that’s it! You can easily setup your own configurable Minecraft server that can be deleted at any time with no impact to your machine. No worrying about .jar files, text editors, etc.</p><p>If you want a tutorial, check out this guy’s post on the subject:</p><p><a href="https://blog.docker.com/2015/06/minecraft-server-docker-1/">Setting Up a Minecraft Server Using Docker - Part 1</a></p><p>Have questions or a particular post you’d like a write-up on? <a href="https://twitter.com/intent/tweet?screen_name=tatemz">Hit me up on twitter</a>!</p><p>Check out <a href="https://medium.com/@tatemz/my-most-used-docker-commands-301b104f9561#.jrvprvofj">my post on my most used Docker commands</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9f2a519d3ce" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Most Used Docker Commands]]></title>
            <link>https://medium.com/@tatemz/my-most-used-docker-commands-301b104f9561?source=rss-87150537fd29------2</link>
            <guid isPermaLink="false">https://medium.com/p/301b104f9561</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[A. Tate Barber]]></dc:creator>
            <pubDate>Tue, 09 Aug 2016 21:35:17 GMT</pubDate>
            <atom:updated>2016-08-09T21:35:17.220Z</atom:updated>
            <content:encoded><![CDATA[<p>Below is a list of commands that I use often when performing container management and cleanup. This list does not include docker-compose commands, but rather some of the quick one-liners that I use for managing my docker containers, images, and volumes. I will try to keep this updated when I think of more.</p><p>List all running containers</p><pre>$ docker ps</pre><p>Kill all running containers</p><pre>$ docker kill $(docker ps -aq)</pre><p>Shell into an ubuntu container (for testing stuff) and delete container after I exit the session</p><pre>$ docker run -it --rm ubuntu bash</pre><p>Shell into a running container to tweak or modify things</p><pre>$ docker exec -it my-container bash</pre><p>Build and tag an image using the Dockfile in the current directory</p><pre>$ docker build -t tatemz/my-image ./</pre><p>Remove all untagged images</p><pre>$ docker rmi $(docker images -q -f dangling=true)</pre><p>Remove all orphaned volumes</p><pre>$ docker volume rm $(docker volume ls -qf dangling=true)</pre><p>Remove containers whose names were auto-generated</p><pre>$ docker rm $(docker ps -aq -f name=admiring -f name=adoring -f name=affectionate -f name=agitated -f name=amazing -f name=angry -f name=awesome -f name=backstabbing -f name=berserk -f name=big -f name=boring -f name=clever -f name=cocky -f name=compassionate -f name=condescending -f name=cranky -f name=desperate -f name=determined -f name=distracted -f name=dreamy -f name=drunk -f name=eager -f name=ecstatic -f name=elastic -f name=elated -f name=elegant -f name=evil -f name=fervent -f name=focused -f name=furious -f name=gigantic -f name=gloomy -f name=goofy -f name=grave -f name=happy -f name=high -f name=hopeful -f name=hungry -f name=infallible -f name=jolly -f name=jovial -f name=kickass -f name=lonely -f name=loving -f name=mad -f name=modest -f name=naughty -f name=nauseous -f name=nostalgic -f name=peaceful -f name=pedantic -f name=pensive -f name=prickly -f name=reverent -f name=romantic -f name=sad -f name=serene -f name=sharp -f name=sick -f name=silly -f name=sleepy -f name=small -f name=stoic -f name=stupefied -f name=suspicious -f name=tender -f name=thirsty -f name=tiny -f name=trusting -f name=zen)</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=301b104f9561" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using wp-cli with Docker]]></title>
            <link>https://medium.com/@tatemz/using-wp-cli-with-docker-21b0ab9fab79?source=rss-87150537fd29------2</link>
            <guid isPermaLink="false">https://medium.com/p/21b0ab9fab79</guid>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[A. Tate Barber]]></dc:creator>
            <pubDate>Fri, 05 Aug 2016 22:31:14 GMT</pubDate>
            <atom:updated>2016-08-10T12:03:50.338Z</atom:updated>
            <content:encoded><![CDATA[<p>Earlier this week, I posted a tutorial on <a href="https://medium.com/@tatemz/local-wordpress-development-with-docker-3-easy-steps-a7c375366b9#.sgazilrgo">how to setup a local WordPress environment using Docker</a>. If you read that, then this post will serve you well.</p><p>When you’re finished, be sure to check out <a href="http://“My Most Used Docker Commands” @tatemz https://medium.com/@tatemz/my-most-used-docker-commands-301b104f9561">my post on some helpful docker commands</a> for cleaning up your dev environment.</p><p>Many of us use <a href="http://wp-cli.org/">wp-cli</a> to manage our WordPress installations. If you are using <a href="https://docker.com/">Docker</a> to manage your local development, then you are probably wondering how you can leverage wp-cli since your container is now a virtual environment. People are still not used to using Docker, and so the idea of using it to manage your cli tools is still a bit confusing. Thankfully, I have already done the work for you!</p><p>If you benefit from this tutorial or you’d like to add to the conversation, be sure to <a href="https://twitter.com/intent/tweet?screen_name=tatemz">hit me up on Twitter</a> and I’ll get back to you.</p><h4>The Quick and Dirty</h4><p>Before you use the following snippet, <a href="https://gist.github.com/tatemz/504383c921aa5898c49b82d4ee181362#file-docker-wordpress-sh">be sure to checkout the first snippet</a>.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d9350131706baeb814cbd236a2f9c964/href">https://medium.com/media/d9350131706baeb814cbd236a2f9c964/href</a></iframe><p>Let’s dive into more detail…</p><h4>Setting Up docker-compose</h4><p>If you followed my last post, you will have a docker-compose.yml file that looks like this inside of your WordPress directory:</p><pre>my-wpdb:<br>  image: mariadb<br>  ports:<br>    - &quot;8081:3306&quot;<br>  environment:<br>    MYSQL_ROOT_PASSWORD: ChangeMeIfYouWant<br>    <br>my-wp:<br>  image: wordpress<br>  volumes:<br>    - ./:/var/www/html<br>  ports:<br>    - &quot;8080:80&quot;<br>  links:<br>    - my-wpdb:mysql<br>  environment:<br>    WORDPRESS_DB_PASSWORD: ChangeMeIfYouWant</pre><p>Let’s add a wp-cli container to our stack…</p><pre>my-wpcli:<br>  image: tatemz/wp-cli<br>  volumes_from:<br>    - my-wp<br>  links:<br>    - my-wpdb:mysql<br>  entrypoint: wp  <br>  command: &quot;--info&quot;</pre><p>A few new things are new here since the last time:</p><ul><li>First, we are telling this container to use the same synced volumes as our my-wp container (/var/www/html to be exact). This way, wp-cli has access to our WordPress files.</li><li>Additionally, we are linking the my-wpdb container to it in order for wp-cli to share access to the database. If you remember from our last post, this is assigning an alias to the my-wpdb as “mysql” — this is the same as the “DB_HOST” constant in the wp-config.</li><li>Lastly, we are overriding the default entrypoint and command this container will execute on startup. Since my custom tatemz/wp-cli container inherits functionality <a href="https://github.com/tatemz/docker-wpcli/blob/master/Dockerfile#L1">from the wordpress container,</a> the default command that starts Apache will be fired. In this case, our entrypoint will be the “wp” command and the subcommand that we want to run is the “--info” command. On starting our my-wpcli container, it will quickly close after printing the output of the “wp --info” command.</li></ul><p>Docker containers are most often just tiny, simple, linux servers. Therefore, if a command is run that does not exit, the Docker container will stay online. However, if a command exits, the container will halt. You can always check which containers are running on your machine:</p><pre>$ docker ps</pre><p>Now we are all set to run wp-cli commands…</p><h4>Running Commands with docker-compose</h4><p>We need to leverage our my-wpcli container that we added to our stack in order to only run one-off commands. In other words, we don’t need my-wpcli to run as a service — only as a cli tool:</p><pre>$ docker-compose run --rm my-wpcli</pre><p>Let’s break that down: the “run” command tells docker-compose to spin up your container and run a customizable command. Firstly, any arguments we pass to docker-compose must appear <strong>before</strong> the container name. In our case, we are only passing --rm as an argument; this simply removes the container right after it finishes the “wp --info” command. If we did not do this, we would create an orphaned container.</p><pre>$ docker-compose run --rm my-wpcli</pre><p>Anything that would come <strong>after</strong> the container name would override the “command” setting that we set above. In this case, the default is “--info”, but we can override it to something useful like this:</p><pre>$ docker-compose run -rm my-wpcli post list</pre><p>This is the same as running the following wp-cli command</p><pre>$ wp post list</pre><p>To make the process easier, we can store this command as an alias:</p><pre>$ alias wp=&quot;docker-compose run -rm my-wpcli&quot;<br>$ wp post list</pre><p>Now we are flying with our alias!</p><pre>$ wp core install --url=&quot;localhost:8080&quot; --title=&quot;WordPress&quot; --admin_user=&quot;admin&quot; --admin_password=&quot;prollynotadmin&quot; --admin_email=&quot;<a href="/service/mailto:admin@email.com">admin@email.com</a>&quot;</pre><pre>$ wp user create jimmy <a href="/service/mailto:jimmy@email.com">jimmy@email.com</a> --role=&quot;administrator&quot;</pre><pre>$ wp media regenerate -y</pre><pre>$ wp search-replace localhost:8080 productiondomain.com</pre><pre>$ wp db export site-dump.sql</pre><h4>A Simpler Way</h4><p>I chose to expand my explanation in order to show you how to work with docker-compose in order to run one-off commands, however, our stack is now larger because of that. Since my tatemz/wp-cli container image inherits functionality from the official wordpress container, we can simplify this whole process by changing our my-wp stack to use my custom image:</p><pre>my-wp:<br>  image: tatemz/wp-cli<br>  volumes:<br>    - ./:/var/www/html<br>  ports:<br>    - &quot;8080:80&quot;<br>  links:<br>    - my-wpdb:mysql<br>  environment:<br>    WORDPRESS_DB_PASSWORD: ChangeMeIfYouWant</pre><p>Since we are not overriding the “entrypoint” or the “command” settings, the default startup script will run and initialize Apache. Like in the previous post, let’s start our stack.</p><pre>$ docker-compose up -d</pre><p>Once our stack is up, we can now execute commands inside the running containers rather than creating a new one and destroying it after it exits.</p><pre>$ docker exec my-wp wp post list</pre><p>Did you benefit from this tutorial? Leave me a comment below or <a href="https://twitter.com/intent/tweet?screen_name=tatemz">on Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21b0ab9fab79" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Local WordPress Development with Docker: 3 Easy Steps]]></title>
            <link>https://medium.com/@tatemz/local-wordpress-development-with-docker-3-easy-steps-a7c375366b9?source=rss-87150537fd29------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7c375366b9</guid>
            <category><![CDATA[php]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[wordpress]]></category>
            <dc:creator><![CDATA[A. Tate Barber]]></dc:creator>
            <pubDate>Wed, 03 Aug 2016 18:20:54 GMT</pubDate>
            <atom:updated>2016-10-23T19:38:47.860Z</atom:updated>
            <content:encoded><![CDATA[<p>Update: Be sure to check out the second part on <a href="https://medium.com/@tatemz/using-wp-cli-with-docker-21b0ab9fab79">using wp-cli with this Docker tutorial</a>.</p><p>Update 10/23/2016: I have updated the snippets to use docker-compose version 2.</p><p>Docker is cool, but since I am a <a href="https://medium.com/@tatemz/confessions-of-a-toolaholic-d39a70e7b79">toolaholic</a> I am not going to waste your or my time preaching about how you must use it. You are a human, after all, so you get to choose which tools you prefer.</p><p>My toolbelt for developing WordPress sites locally has changed over the years. First, I just used an Ubuntu machine with a LAMP stack that I installed via <a href="http://tuxlite.com/about/">Tuxlite</a>. Then I budgeted for a Mac and found MAMP, but once I became more comfortable in bash, a plain ol’ Ubuntu VirtualBox was what I preffered. Then Vagrant came along! Sadly, I was too noob and just ended up back with MAMP. That worked for a while and I just made sure I didn’t touch anything (I was using Nginx on MAMP so configuration was a little more tedious for me compared to my comfort zone with Apache).</p><p>When Docker came along, I quickly grabbed it by the reigns and tested the shit out of all kinds of use cases to the point where I even suggested to my boss that we use it in a few production scenarios. Only until recently, Docker development flat out sucked on Mac and Windows due to the numerous issues with sharing files between the machine and the containers (so I just installed Ubuntu 16.04). On top of that, in Mac &amp; Windows, you had to install Docker inside a Virtualbox via docker-machine. Now, it is <a href="https://blog.hyper.sh/docker-hyper-and-the-end-of-guest-os.html">nearly-native for each platform</a> and many of the kinks have been worked out. Anyway… that is my schtick on why I feel comfortable using it now for local development. Let’s get to the toot!</p><h4>The Quick and Dirty</h4><p>If you just want something to copy and paste and go, I’ll just cut the crap and give it to you.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a49e41eba01b15632061986a87f00bda/href">https://medium.com/media/a49e41eba01b15632061986a87f00bda/href</a></iframe><p>Let’s go into detail… but first, make sure you have Docker installed.</p><p><a href="https://www.docker.com/products/docker">https://www.docker.com/products/docker</a></p><h4>1 - Setup docker-compose</h4><p>Before I go on, I need to say something. You can copy and paste these snippets all day and they will work for you. You can use what I know from trial and error to get something up and working without the sweat, but until you actually go and read the documentation on <a href="https://docs.docker.com/engine/reference/commandline/">docker</a> or <a href="https://docs.docker.com/compose/overview/">docker-compose</a> you probably will not be able to customize and hack together your own process. That said, here we go.</p><p>Navigate to your WordPress project folder. If you don’t have WordPress downloaded yet, that is okay. The <a href="https://hub.docker.com/_/wordpress/">official WordPress container</a> will clone it for you.</p><p>Create a file named docker-compose.yml</p><pre>$ mkdir wordpress-site &amp;&amp; cd wordpress-site<br>$ touch docker-compose.yml</pre><h4>2 - Create Your Containers</h4><p>WordPress needs a LAMP stack to run. In this process, we are splitting that LAMP stack into two containers: one that runs the database (MySQL or MariaDB), and one that runs the webserver (PHP with Apache or PHP with Nginx).</p><p>Paste the YAML configuration for your database container that we are naming “my-wpdb”</p><pre>my-wpdb:<br>  image: mariadb<br>  ports:<br>    - &quot;8081:3306&quot;<br>  environment:<br>    MYSQL_ROOT_PASSWORD: ChangeMeIfYouWant</pre><p>Here we are using the <a href="https://hub.docker.com/_/mariadb/">offical mariadb image</a>, mapping our local port 8081 to the container’s port 3306, and giving it an environment variable containing the root user’s password. “MYSQL_ROOT_PASSWORD” is picked up by a <a href="https://github.com/docker-library/mariadb/blob/d969a465ee48fe10f4b532276f7337ddaaf3fc36/10.1/docker-entrypoint.sh#L37">shell script</a> that runs when the container boots; it will install users with passwords and do some more magic.</p><p>Now we have a database container, but we still need PHP and Apache (and WordPress files).</p><p>Paste the YAML configuration for your WordPress container that we are naming “my-wp”</p><pre>my-wp:<br>  image: wordpress<br>  volumes:<br>    - ./:/var/www/html<br>  ports:<br>    - &quot;8080:80&quot;<br>  links:<br>    - my-wpdb:mysql<br>  environment:<br>    WORDPRESS_DB_PASSWORD: root</pre><p>We are still using official Docker images at this point and this one is the <a href="https://hub.docker.com/_/wordpress/">official WordPress image</a>. It’s also has a <a href="https://github.com/docker-library/wordpress/blob/6afa0720da89f31d6c61fd38bb0d6de6e9a14a49/apache/docker-entrypoint.sh">shell script</a> that automatically <a href="https://github.com/docker-library/wordpress/blob/6afa0720da89f31d6c61fd38bb0d6de6e9a14a49/apache/docker-entrypoint.sh#L146">connects to the database container</a> we created earlier, <a href="https://github.com/docker-library/wordpress/blob/6afa0720da89f31d6c61fd38bb0d6de6e9a14a49/apache/docker-entrypoint.sh#L130">creates a database</a>, <a href="https://github.com/docker-library/wordpress/blob/6afa0720da89f31d6c61fd38bb0d6de6e9a14a49/apache/docker-entrypoint.sh#L22">clones WordPress files</a>, and <a href="https://github.com/docker-library/wordpress/blob/6afa0720da89f31d6c61fd38bb0d6de6e9a14a49/apache/docker-entrypoint.sh#L90">sets up the wp-config</a> based on environment variables that we pass to it (see the official image page for all the options).</p><p>Just like the database container, we are mapping our machine port 8080 to the container port 80. Additionally, we are mounting our current directory ./ to the container’s webroot directory /var/www/html. Docker calls these “volumes”. This allows your project to live on your local machine and be shared to the container.</p><p>Notice that we are linking our my-wpdb container onto our my-wp container. More specifically, we are telling my-wp that it will refer to the my-wpdb container with an alias named “mysql”. This is because the shell script in the WordPress container has <a href="https://github.com/docker-library/wordpress/blob/6afa0720da89f31d6c61fd38bb0d6de6e9a14a49/apache/docker-entrypoint.sh#L5">hardcoded the database hostname</a> as “mysql”. Docker is just magically assigning a hostname to the my-wpdb IP address.</p><p>Whew!</p><h4>3 - Run and Connect</h4><p>Now you can create your containers and run them, and docker-compose makes this extremely easy!</p><pre>$ docker-compose up -d</pre><p>You can now browse to <a href="http://localhost:8080/">http://localhost:8080/</a> and see your WordPress installation dialog! If you want to connect to mysql, just be sure to use the address 127.0.0.1 and the port 8081 like we mapped above. The hostnames and IP addresses may differ depending on how you have installed Docker, but these will work if you use the distributed Docker installations.</p><p>If you want to see the output of the containers (to monitor for errors), follow their logs:</p><pre>$ docker-compose logs -f</pre><p>If you ever want to stop and restart your containers just run</p><pre>$ docker-compose stop<br>$ docker-compose up -d</pre><p>Ask me questions via comments or on Twitter <a href="https://twitter.com/tatemz">https://twitter.com/tatemz</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7c375366b9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Confessions of a Toolaholic]]></title>
            <link>https://medium.com/@tatemz/confessions-of-a-toolaholic-d39a70e7b793?source=rss-87150537fd29------2</link>
            <guid isPermaLink="false">https://medium.com/p/d39a70e7b793</guid>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[A. Tate Barber]]></dc:creator>
            <pubDate>Mon, 11 Jul 2016 00:07:54 GMT</pubDate>
            <atom:updated>2016-07-11T12:01:01.433Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*JjqVItgk3xD-ZA5bdmhvUA.jpeg" /></figure><p>Technology moves extremely fast… too fast to keep up with every single new development tool or application that comes to the web each day. Those that are actually on top of their game and know how to use <em>the latest thing</em> are usually a lot like me, a “toolaholic” — they switch up their dev environment almost every week in order to try out the latest CI tool, task runner, IDE, npm package, docker container, or cloud hosting provider.</p><blockquote>Your opinion is most valuable when you have actually tried a tool in a real and viable programming scenario.</blockquote><p>There are good and bad things about toolaholics, and rather than going through my opinions, I’d much rather just give you a list of some key identifiers to check if you are a toolaholic. Now, before you determine that I am judgmental, know that I am writing all of this from personal experiences and mistakes. Lol! I am probably the biggest toolaholic I know.</p><h4>How to Know If You Are a Toolaholic</h4><ul><li>You spend more time tooling or setting up your workstation or dev environment than you do writing some kickass code.</li><li>You spend even more time scouring tech blogs in order to catch the hottest buzz words in tech than you do the previous point.</li><li>Your coworkers and friends roll their eyes when you say, “Omg! Have you guys heard about ___?”</li><li>You regularly are late or last-minute when turning in your projects because your latest tool of choice breaks your project the day before your project’s due date.</li><li>You regularly offer your opinions on the latest tech buzzword based on that one biased article that you read that one time.</li><li>You try to hide the fact that you have only used said tool in a “Hello World” tutorial.</li><li>You regularly use a fresh and untested tool in production environments without any concerns for maintainability or security.</li><li>You basically think that everyone that is not using the same tools that you use is pretty much useless as a developer and will probably be fired from their job within the next year.</li><li>You speak at tech conferences on how to use your latest and greatest tool of choice and mid-presentation, you hit a snag and just end up saying, “Well, I’ll just post the code up on GitHub and you guys can go try it yourself at home.” Two weeks later you still haven’t posted your code because you are already on the next tool.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*KOj7a1dTagFZwQ1Lwyh7TA.jpeg" /><figcaption><a href="http://www.commitstrip.com/en/2013/09/20/hello-world-ne-suffit-pas/">http://www.commitstrip.com/en/2013/09/20/hello-world-ne-suffit-pas/</a></figcaption></figure><p>These identifiers may all sound negative, however, there are many beneficial aspects to being a toolaholic, and I am under the impression that rampant toolaholics can be some of the best and most diversely skilled programmers out there.</p><h4>The Steps to Recovery</h4><ol><li><strong>Get shit done! </strong>Sit down and have yourself a mini hackathon where you actually produce something viable in a few hours. Once you do that, you will realize that you can actually duplicate that process at will! Take notes on what kept you motivated, focused, and productive; try and duplicate those attributes a few times a week.</li><li><strong>Schedule specific research time. </strong>Specifically pick a few hours a week to read your tech blogs, latest GitHub projects, and twitter articles. Try to not obsessively check these throughout the day and instead, focus on your task at hand.</li><li><strong>Schedule specific tutorial/testing time. </strong>Similarly, you will want to set aside time in order to test out and download the latest and greatest tool or project source code.</li><li><strong>Be honest! </strong>Stop acting like you know a tool when you have only read a few articles on why it is great or have gone through the tutorial. Your opinion is most valuable when you have actually tried a tool in a real and viable programming scenario.</li><li><strong>Don’t judge others. </strong>When you go around being dogmatic about how to accomplish tasks, you end up being condescending and judging towards others that do not use the tool you are showing off.</li><li><strong>Be agnostic to tools. </strong>I tend to think that the tools that I have read about or have actually used are indeed the best tools out there. That logic is ironic and awfully convenient, no? It’s best to be indifferent to which tools are the best and instead just be willing to admit which features are better than others. At the end of the day, it doesn’t matter if your best friend uses “nano” and you use “vim” — both are capable of cranking out code and getting shit done!</li><li><strong>Try it the hard way.</strong> Learn to write and ship your code <em>without</em> the fanciest tool so that your opinion on why that tool is useful and beneficial is even more valuable.</li></ol><p>Vanilla Javascript is becoming more of a trend these days due to the problems with toolaholics; for reference, check out <a href="http://youmightnotneedjquery.com/">http://youmightnotneedjquery.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d39a70e7b793" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Got Git?]]></title>
            <link>https://medium.com/@tatemz/got-git-ee1e6e0d118d?source=rss-87150537fd29------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee1e6e0d118d</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[A. Tate Barber]]></dc:creator>
            <pubDate>Tue, 05 Jul 2016 14:27:00 GMT</pubDate>
            <atom:updated>2016-07-05T14:27:00.420Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lAPLKfQ1V1wH_hyzzAZ0Dg.png" /><figcaption>Photo by <a href="https://hikaruzone.wordpress.com/2015/10/06/in-case-of-fire-1-git-commit-2-git-push-3-leave-building/">Marco Leong</a></figcaption></figure><p>Git is awesome. If you don’t believe me, just ask the internet. Now there are hundreds of thousands of development tools, protocols, frameworks, libraries, and platforms out there, and when I begin thinking of this, I am amazed that there are only a few that stand out, are adopted worldwide, and considered an industry standard. Git has been used long enough to earn its merit badges, and though it is so common, I feel that git needs this little blog post to praise it’s everyday benefits.</p><h4>Git Makes Me a Better Programmer</h4><p>If you use git, you have already taken the next step into becoming a better programmer. You are backing up your code, creating versions you can “checkout” and review, and (more than likely) allowing other programmers to see your code progress.</p><p>If you are like me, while you were new to git, you would just code away and commit every few days or so with commit messages like this:</p><pre>$ git add -A<br>$ git commit -m &quot;Huge freaking commit! Lots of stuff was changed!&quot;</pre><p>This was nifty for a while, but eventually I stopped seeing the importance of git; to me, it was simply a way to publish and pull code around without dragging and dropping via FTP. Though this was a step, I was still hindering myself from becoming a better programmer and using git correctly. Unfortunately, I still do this at times when I get lazy and unmotivated with a project.</p><h4>Branches</h4><p>Branches also enhance my skill level as a programmer. The whole idea of a branch is to test out new changes without affected another environment of my code. Most commonly, a “master” and “develop” branch can be found in most git repositories, however when I begin to use <strong>feature branches</strong>, I am on the right track.</p><blockquote>…when I break apart my application into bite-sized chunks, I lessen bugs, have shorter development life cycles, and allow collaborators to easily hop in and out of aiding with changes.</blockquote><p>Feature branches have been popularized and standardized over the past 5 years. Simply put, they are a branches that are used to house and develop individual features. When using numerous feature branches, I am proving that I am properly segmenting my project into smaller parts. Similar to the concept of object-oriented programming, when I break apart my application into bite-sized chunks, I lessen bugs, have shorter development life cycles, and allow collaborators to easily hop in and out of aiding with changes. Merging branches become less dangerous and therefore less troublesome the smaller the feature.</p><p>If you’d like to get more in-depth concerning git workflow and branches, checkout (no pun intended) <a href="http://danielkummer.github.io/git-flow-cheatsheet/">git-flow</a>.</p><h4>Git Proves That I Get Shit Done (or Not)</h4><p>When I was a young a sapling of a developer, I didn’t see the point in committing my code often (hence, my “Huge freaking commit!” messages). However, a few years later, I wish that I could say that I have committed code to any old repository at least every weekday. When you commit code, a feeling of accomplishment is experienced and that experience is actually recorded with a timestamp. Every day that I have not committed something is a day that I was not performing at my best and was being lazy.</p><p>Commit code often — even if it is a few lines. You will be a happier, more efficient, and better developer because of it. And let’s be honest, the better developer you are, the higher your salary will be.</p><blockquote>When you commit code, a feeling of accomplishment is experienced and that experience is actually recorded with a timestamp.</blockquote><p>This guy <a href="https://github.com/mroth/lolcommits">took a selfie every time he committed</a> code and put together a time-lapse video.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F45151489&amp;url=https%3A%2F%2Fvimeo.com%2F45151489&amp;image=http%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F354361385_640.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="640" height="360" frameborder="0" scrolling="no"><a href="https://medium.com/media/a9a4b9e736c88e0060151653eec361b0/href">https://medium.com/media/a9a4b9e736c88e0060151653eec361b0/href</a></iframe><h4>Git Makes Me a Better Sysadmin</h4><p>GUI tools like <a href="https://www.git-tower.com/">Tower</a> or <a href="https://www.sourcetreeapp.com/">Atlassian’s Sourcetree</a> are really helpful, however can hinder my learning curve. One of the best tips I have ever been given was from a supervisor at one of my first jobs. He advised me to never adopt a GUI tool until I knew what each button within the GUI did in the terminal. Specifically, this was about git and Sourcetree. Because I was depending on the GUI tool, I avoided the terminal commands, and as a result, I didn’t know how to use git.</p><p>Once I took my supervisors advice, I quickly learned how to use git and quickly became proficient. Thankfully, this principle can also be applied in other areas. For instance, I shouldn’t use “docker-compose” commands until I know how to use the raw “docker” commands.</p><p>Being comfortable in the terminal by using git allowed me to get a feel for man pages, help commands, filesystem navigation, and command parameters. These skills can then be applied to almost any command line tools.</p><blockquote>Every day that I have not committed something is a day that I was not performing at my best and was being lazy.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee1e6e0d118d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Suck at CSS]]></title>
            <link>https://medium.com/@tatemz/how-to-suck-at-css-cb956ccce067?source=rss-87150537fd29------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb956ccce067</guid>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[css]]></category>
            <dc:creator><![CDATA[A. Tate Barber]]></dc:creator>
            <pubDate>Tue, 05 Jul 2016 02:45:19 GMT</pubDate>
            <atom:updated>2016-07-05T02:45:19.992Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*kZq06CvyGt8PQXKr5c6NqA.jpeg" /></figure><p>If you are anything like me, you have made some plain awful mistakes in your career as a developer. The most embarrassing of code I have ever written has little to do with complex object-oriented setups, but with the simple and relatively “dumb” language of CSS. You would think that a simple language that is practically written in English, would be easy to maintain and easy to manipulate. Here are my most embarrassing CSS moments:</p><h4>Positioning Pixels</h4><p>In my early days as a freelancer, the first tasks I gravitated towards were small frontend changes. They were bite-sized, easy money, and made it easy to learn new things. I found some tutorials on the web and began moving things around all over the place. Rather than using margins, floats, and widths to move things around, I used exact pixels to bump an elements’ top, bottom, left, and right positions. What made it worse was that most often do this in conjunction with “position: absolute;”</p><h4>Absolute Widths</h4><p>One time, I was busy working on some CSS and researching some tutorials online when I came across something like the following…</p><pre>.sidebar {<br>  with: 25%;<br>  float: left;<br>}</pre><p>And my brain went like this…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*EsaE3xBIUt5qRByef3f4uQ.gif" /><figcaption>“What?! You can set widths as a percentage?!”</figcaption></figure><p>Why this was not shown in one of the first set of tutorials I read is still a shocker to me. It was 2010 and all the tutorials on the web were very outdated. For almost half a year, I was ruining my websites by giving elements absolute widths. When the term “responsive design” hit the market, I was already a bit behind the margin of good frontend developers.</p><h4>Over-Nesting</h4><p>When preprocessors came along, they were all the rage. I was one of the first to hop on the trend and use it in production. It was awesome — you could set variables, nest rules, create reusable mixins and calculations. What was not to love?</p><p>Unfortunately, because I was still such a young sprout in the world of code, I became a little too comfortable with those nested rules. I targeted most of my styles based on the “context” of the element rather than the name or function of the element. My site looked great, and that was all that mattered. And since the web was much faster, the 800kb stylesheet loaded relatively well.</p><p>The biggest pain point when making this mistake comes in to play when making edits. Because every style is based on context and has 4 parent selectors, making a change requires you to trump that level of specificity.</p><p>Perhaps one of the greatest lessons that I have learned to help me conquer this problem was through the understanding of <a href="https://github.com/stubbornella/oocss/wiki">object-oriented CSS</a> as well as the practice of CSS styleguides like <a href="https://smacss.com/">SMACSS</a>. With these ways of thinking, I now average 8kb to 15kb per stylesheet and they load even zippier.</p><p><a href="https://specificity.keegan.st/">Also! Take a look at this CSS specificity calculator.</a></p><h4>!Important</h4><p>Following my over-nesting conundrum, I found myself regularly using “!important” tags in order to trump styles whenever I could not figure out how far down the nest of selectors I should go. If you don’t know how bad this is, just go take a look at Harry Roberts <a href="http://cssguidelin.es/#important">guidelines on the issue.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*rtCDWcDOG04d2zgAroCjgA.jpeg" /></figure><p>Still to this day, I see people that I collaborate with using “!important” tags all over the place. It’s dirty and dangerous… especially when you are dealing with a site that attempts to maintain some semblance of UI consistency.</p><h4>Wrappers</h4><p>This one is a less common problem for frontend developers, but if you are like me and you find yourself obsessing over perfect frameworks and systems, then you like things to be infinitely configurable and manipulatable. There were many times in my frontend history where I added useless wrapper-containers to all sorts of elements. In conjunction with my tendency to over-nest my selectors, I used these wrappers to contextually add paddings and margins and other design specifications. Half the time, the wrappers I added were not even used.</p><h4>Flexbox</h4><p>I like to jump on the latest versions and betas as much as I can. When flexbox came to CSS, I was overjoyed due to the possibility to horizontally center elements as well as force them to be equal in height. Because these two features were in almost every site I developed, I leaned heavily on flexbox. This ended up being a huge pain because I used flexbox on EVERY SINGLE ELEMENT that had a sibling element within the same row. Oh how, I was foolish! The discrepancies between the four major browsers were insane and I ended up spending more time obsessing over one <a href="https://github.com/philipwalton/flexbugs">flexbug</a> rather than writing working code. Now I know only to use flexbox when I absolutely need it and as long as floating elements still can maintain a structure.</p><h4>“Wet” Code</h4><p>Okay, so that is not a real term… but my code certainly was not <a href="https://en.wikipedia.org/wiki/Don%27t_repeat_yourself">DRY</a>. Still today, my CSS could be further optimized by ensuring that duplicate styles are not written for two very similar elements. I would have two boxes with identical padding and rather than just creating a class named something like “standard-padding”, I ended up just writing that code (and changing it later) in two places. This multiplied by a thousand rules makes for some very unDRY code.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb956ccce067" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Holy Grail of Web Development]]></title>
            <link>https://medium.com/@tatemz/the-holy-grail-of-web-development-4a80c056fdde?source=rss-87150537fd29------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a80c056fdde</guid>
            <category><![CDATA[deployment]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[A. Tate Barber]]></dc:creator>
            <pubDate>Fri, 01 Jul 2016 20:25:35 GMT</pubDate>
            <atom:updated>2016-07-01T20:44:49.288Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rJsGos_HeBPX9LCkap1WhQ.jpeg" /></figure><p>Sometimes, you simply need a website up and running so that you can get right to work on developing some cool shit! Alas, it is never an easy task because you must initialize an empty repo, configure up a database, configure your webserver with specific requirements to your application, install the relevant tools on your workstation, and all the while consider that your production environment could be entirely out of your control. If you are anything like me, you just got depressed and want to quit your job. Your “Junior Web Developer” title was just transformed to “Full Stack Jack-of-All-Trades Devops Software Engineering Ninja Guru UX-Master Developer” as soon as your boss popped in your office to ask you to prototype a landing page by the end of the day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*1Hxrh0BLvi7QC_aYU-lLvg.jpeg" /><figcaption><a href="http://www.commitstrip.com/en/2012/02/27/interview-let-there-be-light/">http://www.commitstrip.com/en/2012/02/27/interview-let-there-be-light/</a></figcaption></figure><p>So rather than writing some awesome SPA webpage, or a kick-ass Rails app that runs off an API, or even a simple WordPress plugin, you spend the rest of your day node-ing, puppeteering, Dockering, devopsing, scripting, Cheffing, gulping, bug-reporting, etc. Sometime before 5:00pm, you frantically say to yourself, “Screw it! I’ll just use this inline Javascript &amp; CSS, and a bare HTML file and drag it directly into Chrome.” Your ego has been crushed and you just know that your boss, who just got done showing you his nephew’s latest web project with some 360º virtual reality video feature, is going to think you are dumb as hell.</p><blockquote>At the end of the day, your boss wants your code on a dev server so that he can look at it via a domain name address…</blockquote><p>If <a href="http://www.theverge.com/2016/3/9/11184362/google-alphago-go-deepmind-result">Google can teach a robot to master Go</a>, then this process should not be a difficult one. Large companies have entire teams dedicated to deployment, testing, integrating, etc, but you are just a one-man guy in the morning and same in the afternoon so what are you going to do? At the moment, I have yet to find a solution to this sad predicament, however this is the “holy grail” feature every small company web developer needs:</p><ul><li>A production-ready, Dockerized environment that can be initiated with a simple docker-compose command (without a butt-load of environment variables)</li><li>A configuration based setup with local and production environments (yaml, please!)</li><li>Database version control and/or syncing</li><li>Dockerized tooling environment (ruby gems, npm, bower, gulp, etc) with zero long-term impact on your workstation</li><li>Simple plug-and-play setup that allows deployment to AWS or Azure or Digital Ocean.</li><li>A configuration setup that handles DNS, multi-master replication with automatic scaling (with budget caps), <a href="https://www.nomadproject.io/">Nomad</a>?, CDN media syncing, and more…</li><li>Automatic continuous integration/deployment configuration with private repo capabilities (ssh-keys)</li><li>An electricity-free, solar-powered, pocket-sized, bitcoin miner. :-)</li></ul><p>With these features, the process could look like this:</p><pre>$ holy-grail new myApp &amp;&amp; cd myApp<br>$ holy-grail config --template=rails --database=mongodb<br>$ holy-grail environment add local<br>$ holy-grail serve</pre><pre>... Development and git branches and local db changes ...</pre><pre>$ holy-grail environment add production<br>$ holy-grail provider add aws YOUR_AWS_KEYS_GO_HERE<br>$ holy-grail publish --environment=production --provider=aws</pre><p>There are certain application stacks and skeletons that attempt to solve these aforementioned goals, however, none of them are very good at deploying your code. At the end of the day, your boss wants your code on a dev server so that he can look at it via a domain name address (not your local live-reload IP address). He doesn’t care (or shouldn’t) whether you wrote your own Docker image, setup a Jenkins server, or whether you wrote plain CSS or some fantabulous Sass framework.</p><blockquote>Sometimes, you simply need a website up and running so that you can get right to work on developing some cool shit!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a80c056fdde" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>