<?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 Tyler Ward on Medium]]></title>
        <description><![CDATA[Stories by Tyler Ward on Medium]]></description>
        <link>https://medium.com/@twardnw?source=rss-80f360e4f41d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RAJbfU0m9U8i6FUmanZhJw.png</url>
            <title>Stories by Tyler Ward on Medium</title>
            <link>https://medium.com/@twardnw?source=rss-80f360e4f41d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 09:17:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@twardnw/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[BADCamp 2019 Recap]]></title>
            <link>https://medium.com/amazee-io/badcamp-2019-recap-70495a5edfc7?source=rss-80f360e4f41d------2</link>
            <guid isPermaLink="false">https://medium.com/p/70495a5edfc7</guid>
            <category><![CDATA[community]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[web-hosting]]></category>
            <category><![CDATA[drupal]]></category>
            <dc:creator><![CDATA[Tyler Ward]]></dc:creator>
            <pubDate>Fri, 11 Oct 2019 15:47:42 GMT</pubDate>
            <atom:updated>2019-10-11T15:47:42.006Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y9Ty9q7mBBd49rWwIrhEog.jpeg" /></figure><p>BADCamp is an annual four-day event held in Berkeley, California and led by some of the best teachers in the community that offers sessions, training classes, summits, sponsors, and social gatherings. This was my fourth year attending. The major difference from previous years was a change of venue, the Hotel Shattuck Plaza. This year’s offerings, while still Drupal centered, had a lot more business and “Being Human” programming than years past.</p><p>After traveling and getting settled on Wednesday, Thursday brought the amazee.io sponsored <a href="https://2019.badcamp.org/summit/devops-summit">DevOps Summit</a> which was well attended and featured topics like performance tuning, application scaling, automated testing, continuous integration, local development, ChatOps. A highlight of the day was the Kubernetes Konversation with Michael Schmid along with ​Kevin Bridges​, ​Tess Flynn, and​ Yevgen Nikitin, and more! There were a lot of diverse opinions presented, which is to be expected because it’s brand new — overall I think lots of good information was shared and hope that attendees found it helpful as they see what options Kubernetes offers now and where it can lead in the future. Michael also presented a session on how to cache decoupled sites to maximize speed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YMfwFSI8QgFY3Pnnf_1LVw.jpeg" /></figure><p>Thursday evening we had the opportunity to have some Lagoon and amazee.io themed drinks at a happy hour. It was great to get to hang out with folks from the conference outside of the usual venues. There were current and hopefully future users of Lagoon and we got to talk about future features and everything Lagoon has to offer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mgv6xdIiWH-hNzAuitPrzA.jpeg" /></figure><p>On Friday I attended a talk called <a href="https://2019.badcamp.org/session/grown-ups-are-not-coming">The Grownups Are Not Coming</a> It was a nice reminder to stop for a minute and laid out a decision-making process for those times when you’re in unknown territory. When no one is coming to help you make a decision, there was good information about how to decide what input to consider and what to ignore.</p><p>I’m in a new-ish role as a manager and found the session <a href="https://2019.badcamp.org/session/how-work-remotely-and-foster-happy-balanced-life">How to Work Remotely and Foster a Happy, Balanced Life</a> helpful, especially for strategies on managing on a distributed team. The session emphasized that “It is not the act of working from home that creates employee happiness; it is creating a culture that fosters remote practices to develop meaning, collaboration, and happiness.”</p><p>I also attended a <a href="https://2019.badcamp.org/session/level-your-development-experience-lando">session on Lando</a>, a local development environment tool that uses Docker. I have known about it but wanted to get more input and the interesting thing about this session was that it was put on by someone that’s a user, not a developer. It’s cool that their tool has had enough adoption that they have community members who can give sessions and spread the world.</p><p>Between sessions and social events, I got to hang out with team members, several of which I hadn’t met in person before. As a distributed team we spend a lot of time together online, but it’s always nice to get a chance to see each other IRL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SL3l_f5Olen8uJtn1gNGpg.jpeg" /></figure><p>We spent some time working on a light display for <a href="https://stories.amazee.io/join-us-at-drupalcon-amsterdam-2019-3f50a4b73d5c">DrupalCon Amsterdam</a>. We took an addressable LED strip and hooked up to raspberry pi that talks to our logging system. It takes traffic data from a handful of sites that we’re hosting on Lagoon and turns that traffic data into a lighted section with speed and color varying based on what kind of traffic it is. Check out our booth in Amsterdam in October to see the results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dW90_xH1FwNHojhvVL6Nmg.jpeg" /></figure><p>Thanks for a week of learnings, community, and great food. See you all again next year!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70495a5edfc7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/amazee-io/badcamp-2019-recap-70495a5edfc7">BADCamp 2019 Recap</a> was originally published in <a href="https://medium.com/amazee-io">Open Source Hosting</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Balancing Engineering and Support at amazee.io]]></title>
            <link>https://medium.com/amazee-io/balancing-engineering-and-support-at-amazee-io-588618f36486?source=rss-80f360e4f41d------2</link>
            <guid isPermaLink="false">https://medium.com/p/588618f36486</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[php]]></category>
            <category><![CDATA[drupal]]></category>
            <category><![CDATA[web-hosting]]></category>
            <category><![CDATA[hosting]]></category>
            <dc:creator><![CDATA[Tyler Ward]]></dc:creator>
            <pubDate>Mon, 08 Oct 2018 15:03:40 GMT</pubDate>
            <atom:updated>2018-10-08T20:08:37.099Z</atom:updated>
            <content:encoded><![CDATA[<p>We do support differently at amazee.io, there is no tier one or ticket system to navigate. The people that build the systems also support the systems and are never more than a chat message away.</p><p>amazee.io has developed a system that allows our engineers to alternately focus on building and improving our next generation hosting solutions and helping our clients immediately and directly through our chat-based support.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*a7neYkkQTKYmtZkyaQm8Tw.jpeg" /></figure><p><strong>Creating a schedule that works for everyone</strong></p><p>As we grew and support needs were increasing it became more and more common that multiple people would be pulled in to help solve problems. Although we love the <a href="https://stories.amazee.io/support-at-amazee-io-means-teamwork-and-collaboration-49cdedbe83ad">spirit of collaboration</a> a stop and start atmosphere wasn’t ideal for engineering and so we came up with the idea for alternating “sprints” to focus on support or engineering. (Disclaimer: although we use the word sprints this isn’t actually an Agile system but rather a continuous schedule)</p><p>The schedule we currently operate on is two weeks of support and two weeks of engineering. It’s not a completely pure system, of course, you might get pulled into support when you are on an engineering sprint but there is an expectation that you can and should have time to build, to innovate, and to unplug if necessary to do it.</p><p><strong>Advantages to the two-week approach</strong></p><p>The advantages of this schedule are clear. There is always someone on hand to solve problems and respond to questions when they come up. At the same time, we are recognizing that to be able to build something complicated you need uninterrupted time. All hours are not created equal if you have to stop and start. This schedule gives engineers the freedom to periodically unplug from slack and client channels if necessary to focus entirely on a complex project.</p><p><strong>Two weeks of support</strong></p><p>During a support sprint, helping clients is our first priority. Whoever is on the line knows all the ins and outs of the system. Many problems have ready solutions that all engineers are familiar with, such as a request to change a PHP setting.</p><p>This is not to say that engineers on this schedule won’t do anything but support, there are always tasks that can be done when things are running smoothly. But during a support sprint, it is expected that you are reachable and that your work will not be compromised by some interruptions.</p><p><strong>Two weeks of engineering</strong></p><p>On an engineering sprint, you can really work on projects. You can even unplug completely for a few hours if you’re prone to distractions. I personally don’t do that often because I’m good at multitasking and I can often help solve problems quickly. Even so, I appreciate the ability to go dark when I need to.</p><p><strong>How does it work?</strong></p><p>One of the reasons we are able to keep to this schedule is because we are a distributed team. This eliminates the distraction of people walking up to your desk and asking you questions, or (more likely for me) of overhearing a conversation and wanting to jump in and help.</p><p>When there is a problem that needs more help, it’s easy enough to pull in extra people or even to get everyone in the same virtual room to collaborate and fix something quickly.</p><p>Before working on this schedule at amazee.io, I used to only be able to do my truly focused work after hours when the office was empty. This schedule makes sure our clients can always talk to an expert, but gives those experts time to build and to innovate too.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=588618f36486" width="1" height="1" alt=""><hr><p><a href="https://medium.com/amazee-io/balancing-engineering-and-support-at-amazee-io-588618f36486">Balancing Engineering and Support at amazee.io</a> was originally published in <a href="https://medium.com/amazee-io">Open Source Hosting</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Outages & Transparency]]></title>
            <link>https://medium.com/amazee-io/outages-transparency-7372097bfd85?source=rss-80f360e4f41d------2</link>
            <guid isPermaLink="false">https://medium.com/p/7372097bfd85</guid>
            <category><![CDATA[php]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[drupal]]></category>
            <category><![CDATA[hosting]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Tyler Ward]]></dc:creator>
            <pubDate>Thu, 07 Dec 2017 22:35:30 GMT</pubDate>
            <atom:updated>2017-12-07T22:35:30.946Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tLIXa6jWWjxfB-6AYjm2Hg.jpeg" /></figure><p>At amazee.io we value transparency in all things. We’d like to take some time to explore why outages happen and explaining our exact processes to make sure they are solved quickly.</p><p>There are three main categories of why outages can happen, and only one of them is directly within our control. But no matter why your site is down, we will be right next to you doing everything we can to get things up and running again.</p><p>The first thing that can cause an outage is a problem with the services we, and therefore our clients, rely on. This could be a something like a hardware with one of our infrastructure partners, intercontinental networking issues, or even DNS outages . In these cases we see a problem pretty quickly, thanks to our monitoring and notification systems. At this point we report the problem to the partner and notify any clients that might be affected. We report it on our <a href="https://status.amazee.io/">status page</a> which is also broadcast on our status <a href="https://twitter.com/status_amazeeio">twitter account</a>. From there we will focus on ongoing monitoring, keeping you informed and being ready to jump into action if we can do anything to help get things back on track.</p><p>The second category of things that can cause an outage is things our clients do. We monitor every site we host and our systems let us know quickly if there’s a problem. If we see a site is down we check for error codes, and then check for normal activities that would cause it like deployment or maintenance. But if no routine updates are scheduled we will reach out to the client directly. Luckily, with our chat support, this is as easy as sending a message in Slack. If the outage wasn’t expected we can move right into support mode. Perhaps the customer was trying to roll out a major new feature to their site or application and things didn’t go as smoothly as planned. . If it doesn’t work, we are always happy to help.</p><p>The third kind of outage-causing problems are things that are our fault. While we’d like to point out this doesn’t happen often, it can sometimes happen and we make sure we bring all of our resources and expertise to bear to communicate with clients clearly and solve the problem quickly. Our first step in these situations is to post to our <a href="https://status.amazee.io/">status page</a> which is also pushed to the <a href="https://twitter.com/status_amazeeio">status twitter</a>. We create an incident on the page and continuously update it as we delve into finding out what caused the problem. From there we go to work!</p><p>Sometimes the root of the problem is simple, such as a typo in some new code that was not picked up during testing, and can be easily solved by one engineer. If it is a more complicated issue, we can call everyone in, if necessary there can be four or five engineers on a video call together, sharing screens, getting it worked out, a virtual think tank of digital problem solving. Once we’ve sorted out the issue, we update the incident on our status page and then monitor our systems closely for stability.</p><p>If the problem was our fault, and affected our clients, we conduct a post mortem, a document that clearly outlines what happened, when we let people know, how we addressed the problem, and what we are doing to prevent similar problems in the future.</p><p>One common way we do this is by asking “why” up to five times. For example:</p><ul><li>Nginx stopped working on a server — why?</li><li>There was an error in a config file — why?</li><li>There was a typo in the api — why?</li><li>There was no test for that setting — why?</li></ul><p>From here, our course of action is clear, we implement a test for that field in the future. Sometimes the solution is to add another check to our monitoring systems. Whatever the problem is we do our best to make sure it’s avoidable in the future.</p><p>While many companies have status pages and issue post mortems, we reach out to our affected clients individually to make sure our communication and support is personal, accessible, and constant. Questions about support or offerings from amazee.io? Hop into our <a href="https://slack.amazee.io/">Slack</a> — we’re always there to help</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7372097bfd85" width="1" height="1" alt=""><hr><p><a href="https://medium.com/amazee-io/outages-transparency-7372097bfd85">Outages &amp; Transparency</a> was originally published in <a href="https://medium.com/amazee-io">Open Source Hosting</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Secure Web is Easy with amazee.io]]></title>
            <link>https://medium.com/amazee-io/the-secure-web-is-easy-with-amazee-io-8b0d94ebeb69?source=rss-80f360e4f41d------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b0d94ebeb69</guid>
            <category><![CDATA[ssl]]></category>
            <category><![CDATA[https]]></category>
            <dc:creator><![CDATA[Tyler Ward]]></dc:creator>
            <pubDate>Thu, 30 Mar 2017 14:05:18 GMT</pubDate>
            <atom:updated>2017-03-30T14:05:18.991Z</atom:updated>
            <content:encoded><![CDATA[<p>Historically, a website would only use HTTPS if handling Personally Identifiable Information (PII) or processing payment transactions. Later, it became standard practice to switch an unsecured site to HTTPS only when taking any input from a user (such as email addresses, usernames, passwords). When browsing the web these days, you’ll see a little padlock icon in your browser’s address bar, indicating the site’s HTTPS secure standing, more often than not.</p><p>Though there was pushback for securing websites via HTTPS in the beginning, it’s now becoming a web best practice.</p><p>Why the pushback? Initially, serving a website via HTTPS increased the overhead on the webserver, and since more data is being transmitted, page load time slowed. Modern internet connections are so fast now this is no longer noticeable.</p><p>SSL certificates were also expensive to obtain, and often required extra effort and cost to install and maintain. Now, SSL certificates can now be obtained cheap — or free — and installation and monitoring can be easily handled through automation tools.</p><p>Recently, search engines have started giving a bit of an SEO bump to sites that are served exclusively via HTTPS and modern browsers will mark a site ‘insecure’ if it accepts user input via HTTP. These small efforts provide even more incentive to serve a website via HTTPS on top of the the already clear benefit of keep users and their data secure.</p><p>There are many more reasons to serve your website over HTTPS, and many <em>many</em> articles have already been published on this topic. I’m not going to attempt to expand on those, but if you’re interested in some additional reading, here’s a few posts to check out:</p><ul><li><a href="https://ahrefs.com/blog/http-vs-https-for-seo/">HTTP vs. HTTPS for SEO: What You Need to Know to Stay in Google’s Good Graces</a></li><li><a href="https://motherboard.vice.com/en_us/article/google-will-soon-shame-all-websites-that-are-unencrypted-chrome-https">Google Will Soon Shame All Websites That Are Unencrypted</a></li><li><a href="https://developers.google.com/web/fundamentals/security/encrypt-in-transit/why-https">Why HTTPS Matters</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mng0QwFfr5c1pP_Nt-CoRQ.png" /><figcaption>amazee.io scores an A on SSL Configuration test</figcaption></figure><p>Last April, the <a href="https://letsencrypt.org/">Let’s Encrypt</a> service launched, offering free, Certified Authority signed, SSL certificates, making the issue of cost of an SSL certificate non-existent. The only barrier that remains is the installation and maintenance of your certificate.</p><p>Making the maintenance slightly more complicated, Let’s Encrypt certificates are only valid for 90 days (and <a href="https://letsencrypt.org/2015/11/09/why-90-days.html">they may shorten that period in the future</a>). On the surface, this may seem like another burden to running your site on HTTPS, but the automation that amazee.io built for this process makes it simple and painless.</p><p>Using Let’s Encrypt on amazee.io couldn’t be simpler. If you host with amazee.io, simply <a href="https://slack.amazee.io/">ping us in Slack</a> and we can enable it for your site, same day.</p><p>Once we enable Let’s Encrypt for your site, we have invested the time to automate every other part of the process: a certificate request is created, the domains verified, and the certificate is created and added to the configuration for your site. We then poll the certificates on each server to see which are expiring soon, and renew them before you even have to think about it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b0d94ebeb69" width="1" height="1" alt=""><hr><p><a href="https://medium.com/amazee-io/the-secure-web-is-easy-with-amazee-io-8b0d94ebeb69">The Secure Web is Easy with amazee.io</a> was originally published in <a href="https://medium.com/amazee-io">Open Source Hosting</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Easing the pain of site launches with upstream redirects]]></title>
            <link>https://medium.com/amazee-io/easing-the-pain-of-site-launches-with-upstream-redirects-c20831892a0e?source=rss-80f360e4f41d------2</link>
            <guid isPermaLink="false">https://medium.com/p/c20831892a0e</guid>
            <dc:creator><![CDATA[Tyler Ward]]></dc:creator>
            <pubDate>Wed, 16 Nov 2016 14:31:01 GMT</pubDate>
            <atom:updated>2016-11-16T14:31:01.239Z</atom:updated>
            <content:encoded><![CDATA[<p>Let’s be honest, migrating a site from one hosting provider to another can sometimes be a fragile process. It often requires close orchestration between developers, two different hosting providers, and most importantly, the client (sometimes including their IT staff).</p><p>There are all sorts of moving pieces; database synchronization, moving git repos, copying static files, and updating DNS. For what we’ve seen, it is usually the DNS that causes the most pain, especially in the moment of launching a site. Either the client can’t remember how/where to update the info or doesn’t realize that it takes time for the changes to propagate.</p><p>To help ease this pain, <a href="http://amazee.io/">amazee.io</a> has set up what we call the <strong>upstream redirect</strong>.</p><p>In practice, this is just a reverse proxy to the existing web hosting via nginx. Requests for the site come in, and the amazee.io servers redirect them to your clients current web host.</p><p>Here’s how it works:</p><ul><li>We look up the CNAME or IP of the current web host</li><li>We will place that record into the nginx configuration for your site (managed via API and Puppet)</li><li>Your client can then freely point their DNS at the <a href="http://amazee.io/">amazee.io</a> servers</li><li>On launch day this configuration option is removed, and the site is immediately served from <a href="http://amazee.io/">amazee.io</a> servers</li></ul><p>This setup allows you to work with your client well ahead of a site launch to manage DNS so any surprises are discovered and addressed in advance of launch. On launch day, your client gets the instant gratification of “flipping the switch” on their site and having it go “live” exactly when they wish.</p><p>For questions about this article, <a href="https://slack.amazee.io/">join our Slack group</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c20831892a0e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/amazee-io/easing-the-pain-of-site-launches-with-upstream-redirects-c20831892a0e">Easing the pain of site launches with upstream redirects</a> was originally published in <a href="https://medium.com/amazee-io">Open Source Hosting</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Easy Local Drupal Development on OS X]]></title>
            <link>https://medium.com/amazee-io/easy-local-drupal-development-on-os-x-a01a343f99e3?source=rss-80f360e4f41d------2</link>
            <guid isPermaLink="false">https://medium.com/p/a01a343f99e3</guid>
            <category><![CDATA[drupal-development]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Tyler Ward]]></dc:creator>
            <pubDate>Wed, 03 Aug 2016 16:25:56 GMT</pubDate>
            <atom:updated>2016-08-18T13:50:11.739Z</atom:updated>
            <content:encoded><![CDATA[<p>Sometimes getting Drupal to run locally can be a bit of a challenge. You may be working on projects which require a stack that Drupal doesn’t like. Perhaps you’re having a hard time getting your webserver, PHP, and database all talking to each other.</p><p>There’s a few tools you can use to make setting up Drupal easier:</p><ul><li>You can bug the ops guys, get them to help you set it all up… but you’ll inevitably be back at their desk or bugging them in Slack a week after some random package updates and it all breaks again…</li><li>You could download a Vagrant image, work to configure it for your site, make a snapshot… but then have restore back to there when your stack goes awry, or maybe you could use a tool like Puppet or Ansible to re-configure that VM, but if you can pull that off, why aren’t you the office DevOps go-to already?</li><li>And then there’s Docker. What a mess! Seemingly random IPs, weird port numbers, hosts file entries, services on different containers, files that disappear when you restart a container. Oy!</li></ul><p>How about an option that takes care of all of this pain for you? Enter<a href="https://docs.amazee.io/local_docker_development/os_x_cachalot.html"> Cachalot</a>. A Docker-compose based local development environment LEMP stack. No knowledge of Docker needed, installable via tools that you probably already have installed, and fast! You can spin up sites in a matter of seconds. It’s what we use here at amazee.io and now we’re sharing it with you.</p><p>Running Ubuntu 14.04 LTS, nginx, Varnish 4, PHP-FPM, and MariaDB 10, Cachalot is a package available via<a href="http://brew.sh/"> Homebrew</a> and only requires you to have a VM provider running locally. We have configurations for PHP 5.6 and 7.0, have Solr available, and fully support sites being built using the most modern methods like Drupal Console and Composer.</p><p>So, what’s it actually look like to get this going. First, you’ll need to install a few dependencies and then Cachalot:</p><pre>brew tap amazeeio/cachalot<br>brew install docker docker-machine cachalot</pre><p>Setup the actual VM that runs Cachalot for us:</p><pre>cachalot create --provider virtualbox</pre><p>And make sure your shell knows about some Docker environment variables:</p><pre>eval(cachalot env)</pre><p>You can also drop that line at the end of your <em>.bash_profile</em>:</p><pre>echo &quot;eval \$(cachalot env)&quot; &gt;&gt; ~/.bash_profile</pre><p>Finally, we need to tell Docker what configuration to use, and we need to tell Drupal how to connect to the database.</p><p>Letting Docker know what our site wants to run on is simple; we’ve provided a number of example docker-compose.yaml files in a<a href="https://github.com/amazeeio/docker"> repo on our GitHub</a>.</p><p>For this example, let’s just assume we’re working with a basic Drupal 8 site that needs PHP 7.0. Our docker-compose.yml will look like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/40e02458e3e93ec96ac0cb4cf4f16661/href">https://medium.com/media/40e02458e3e93ec96ac0cb4cf4f16661/href</a></iframe><p>Take note of the <em>hostname: </em>line, this is the only thing which you <strong>must</strong> edit in the file to have it run.</p><p>If your site’s index.php is not located in the root of your repo, add this line (replace <em>web</em> with the correct directory name) immediately below “environment:” This will let nginx know where to find your index.php.</p><pre>WEBROOT: web</pre><p>Now, for Drupal to know where to find the database, edit your settings.php file and add this snippet at the very end of the file:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1485d03aa4a6658e54249e65e7862973/href">https://medium.com/media/1485d03aa4a6658e54249e65e7862973/href</a></iframe><p>This is just a small part of our provided settings.php files, <a href="https://docs.amazee.io/drupal/settingsphpfiles.html">read more on our documentation</a> about them.</p><p>To finish, simply tell docker-compose to start the container:</p><pre>docker-compose up -d</pre><p>Docker will now go out and download the relevant images and get them all started.</p><blockquote><em>Be patient, the first download is pretty big, and once you have the image stored locally, starting new sites using it is lightning quick.</em></blockquote><p>After the downloads are done, the container for your site will start, and you’ll see a message, <em>“Creating mylocaldrupal.com.docker.amazee.io</em>.”</p><p>You can go ahead and bring the site up in your browser using the hostname entered in <em>docker-compose.yml</em>, just keep in mind you’ll have no database to work with yet.</p><p>To get your site’s database in, you can choose from a few familiar methods. The first step to any of these is to connect to the Docker container. From anywhere in the site’s directory structure, you can run the following command and this will deposit you in the webroot of your site.</p><pre>docker-compose exec --user drupal drupal bash</pre><p>Now, you can use Drush to import a database from a file in your site’s directory structure, <a href="https://docs.amazee.io/step_by_step_guides/get_your_drupal_site_running_on_amazeeio.html#add-existing-database">our documentation</a> explains you how to do that.</p><p>If the site is hosted on amazee.io you can use the power of Drush aliases and import directly from the dev (or production) environment with one single command. One of the great features of Cachalot is that it will securely bring your SSH keys into the site’s container, so you can use any SSH-based method to bring down databases or files from your existing hosting.</p><p>If you run across any problems, amazee.io can help! We’ve got a lot of information in our<a href="http://docs.amazee.io/"> Docs</a>, and there’s almost always someone online in our <a href="https://slack.amazee.io/">public Slack </a>— just join the #docker channel.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a01a343f99e3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/amazee-io/easy-local-drupal-development-on-os-x-a01a343f99e3">Easy Local Drupal Development on OS X</a> was originally published in <a href="https://medium.com/amazee-io">Open Source Hosting</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>