• Fixing "Instead of sudo/sudo_user, use become/become_user" Error

    Fixing "Instead of sudo/sudo_user, use become/become_user" Error header

    I’m working on updating an Ansible configuration that was originally developed using Ansible 1 and I’m now running under Ansible 2. When I did this I kept receiving the following error message:

    Instead of sudo/sudo_user, use become/become_user and make sure become_method is ‘sudo’ (default). This feature will be removed in version 2.6. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.

    The trick to fix this is to change “sudo: yes” in the following:

    - hosts: os_CentOS
      sudo: yes


    - hosts: os_CentOS
      become: yes
      become_user: root
      become_method: sudo
  • Running a Quality Online Book Group For Your Directs

    Running a Quality Online Book Group For Your Directs

    As I discussed in Let’s Invest in Ourselves For 2018, I think that reading is an important part of professional development. I’ve been having my directs read a book each quarter for the last several years and for the last year or so we’ve been reading the same book as a group. I wanted to share my lessons learned while we went through this process.

    Read More
  • Fixing Vagrant Up Error that "laravel/homestead" could not be found

    Fixing Vagrant Up Error that "laravel/homestead" could not be found

    The other day when I was performing a vagrant up I received the following error:

    Scotts-Air:laravelVsSymfony scottkeckwarren$ vagrant up
    Bringing machine 'laravelvssymfony' up with 'virtualbox' provider...
    ==> laravelvssymfony: Box 'laravel/homestead' could not be found. Attempting to find and install...
        laravelvssymfony: Box Provider: virtualbox
        laravelvssymfony: Box Version: >= 5.2.0
    The box 'laravel/homestead' could not be found or
    could not be accessed in the remote catalog. If this is a private
    box on HashiCorp's Atlas, please verify you're logged in via
    `vagrant login`. Also, please double-check the name. The expanded
    URL and error message are shown below:
    URL: [""]
    Error: The requested URL returned error: 404 Not Found

    The only trick to this was to update Vagrant to the current version. I’m hoping this will help someone else who runs into this problem.

  • Onward and Upward

    Onward and Upward

    This is some bittersweet news for me but as of Friday I’m no longer an employee of Zimco. I’m super proud of what we were able to create with STAGES and I’m glad to have been able to work with the amazing team there to create a really amazing product. It’s too bad its time is drawing to a close.

    The good news is that I’ve been hired by Wellspring Lutheran Services to work on their WeCare Connect product that I built while I was at Zimco. I’m looking forward to working with the team there to improve the product. It’s been a great learned experience over these last few years and I’m sure it will continue to be.

  • Link Post and Podcast Roundup: April 2018 Edition

    Link Post Logo

    April’s links.

    Read More
  • How I'm Implementing Robert Martin's Clean Code: A Handbook of Agile Software Craftsmanship

    Implementing Robert Martin's Clean Code Header

    As part of my Let’s Invest in Ourselves For 2017 post I said I wanted to read Clean Code: A Handbook of Agile Software Craftsmanship by Robert Martin. I had a hard time writing a post about what I learned in that book because it’s mostly just a laundry list of things you should (or shouldn’t) do in order to create easier to read code. I’m rereading it with the other programmers at work (at my suggestion) and I realized that there were a lot of things that I’m still not doing that could improve the quality of my code.

    To that end I’ve started a new process. Every Friday, I’m going to pick 5 items from the book and place them on my monitor. Before I make a commit, I’m going to review all my changes and make sure any new code fits those items. The idea is that instead of trying to focus on 100 items all at once I’ll focus on 5 and then

    I’m also posting these to Twitter with the hashtag #ImplementingCleanCode.

  • Midwest PHP 2018 Notes: Open Source, accessibility, and you - the superhero! by Nic Steenhout

    MidwestPHP 2018 Header

    Nic discussed why it’s important for all software but especially open source to be accessible for all users regardless of how they’re accessing your site.

    Read More
  • Midwest PHP 2018 Notes: Developing a Culture of Mentorship by Tessa Kriesel

    Midwest PHP 2018 Header

    • Tessa talked about how to be a mentor and how to be a mentee.
    Read More
  • Midwest PHP 2018 Notes: Technical Annotations and Estimations by Jessica Feigal

    Midwest PHP 2018 Header

    Jessica talked about what annotations are and how to convert those into estimates. Her talk revolved around a waterfall approach but I could see how you could integrate it into an Agile process.

    Read More
  • Midwest PHP 2018 Notes: VM, Serverless, or Containers by Terry Ryan

    Midwest PHP 2018 Header

    Terry gave an overview of Virtual Machines (VM), Serverless options, and Containers. He also did some demos to show them off.

    Read More

subscribe via RSS