Skip to content
View emachnic's full-sized avatar

Block or report emachnic

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse

Pinned Loading

  1. working_man working_man Public

    WorkingMan works for you

    Ruby 22 5

  2. emachnic.github.com emachnic.github.com Public

    1

  3. chef-rubyinstaller chef-rubyinstaller Public

    Chef cookbook for setting up RubyInstaller with DevKit

    Ruby 1

  4. effortless effortless Public

    Forked from chef/effortless

    Automated best practices for Chef Infra and Chef InSpec

    Shell

  5. "Effortless" AMI Deployments with Ch... "Effortless" AMI Deployments with Chef and Habitat
    1
    ## Abstract
    2
    
                  
    3
    Moving to an AMI deployment strategy for standing up web servers can be really awesome. From immutable artifacts that are deployed to any environment, to fewer moving parts, we can really simplify deploys.
    4
    
                  
    5
    Unfortunately, we still usually have some dynamic elements, like web server configs or environment-specific secrets. How can we supply values to those elements at runtime?