miketheman

## Knife plugin to set node environment
# See http://wiki.opscode.com/display/chef/Environments
#
## Install
# Place in .chef/plugins/knife/set_environment.rb
#
## Usage
# Nick-Stielaus-MacBook-Pro:chef-repo nstielau$ knife node set_environment mynode.net my_env
# Looking for mynode.net
# Setting environment to my_env

bjhess

Navigation:

cmd-p             Goto Anything ('@' for functions, ':' for line number)
cmd-r             Function finder
ctl-g             Goto line number
cmd-sft-p         Command palette
cmd-sft-f         Find in Files
cmd-opt-r         Toggle regex when finding
cmd-opt-#         Columns
ctr-#             Switch columns

jtimberman

# Knife Configuration File.
#
# This is a Ruby DSL to set configuration parameters for Knife's
# general options. The default location for this file is
# ~/.chef/knife.rb. If multiple Chef repositories are used,
# per-repository configuration files can be created. A per repository
# configuration file must be .chef/knife.rb in the base directory of
# the Chef repository. For example,
#
#     ~/Development/chef-repo/.chef/knife.rb

jtimberman

ssl_verify_mode         :verify_peer
ssl_ca_file             CA_FILE
log_level               :info
log_location            STDOUT
chef_server_url         'SERVER_URL'
validation_client_name  'ORGNAME-validator'
node_name               'NODE_NAME'

base_dir = "#{ENV['HOME']}/.chef"

jallspaw

Adrian -

I appreciate that you spent time in writing this post. I know I've been up until 2am writing similarly long ones as well. I will take responsibility for having what is likely an irrational response (I blame Twitter for that) to the term "NoOps", but I invite you to investigate why that might be. I'm certainly not the only one who feels this way, apparently, and thus far have decided this issue is easily the largest distraction in my field I've encountered in recent years. I have had the option to simply ignore my opposition to the term, and just let the chips fall where they may with how popular the term "NoOps" may or may not get. I have obviously not taken that option in the past, but I plan to in the future.

You're not an analyst saying "NoOps". Analysts are easy (for me) to ignore, because they're not practitioners. We have expectations of engineering maturity from practitioners in this field of web engineering, especially those we consider leaders. I don't have any expectations from analysts,

cookrn

• git format-patch man page
• helpful article

jtimberman

# via Jay Feldblum on chef@lists.opscode.com:

name "base"
description "Base role applied to all nodes."

all = [
    "recipe[apt]",
    "recipe[build-essential]",
    "recipe[git]",
    "recipe[zsh]",

jtimberman

#
# Author:: Joshua Timberman <opensource@housepub.org>
# Copyright:: Copyright (c) 2012, Joshua Timberman
# License:: Apache License, Version 2.0
#
# Ohai Plugin: external_ipaddress
#
# Save this to /etc/chef/ohai_plugins/external_ipaddress.rb, then run ohai with:
#
#    ohai -d /etc/chef/ohai_plugins external_ipaddress

jtimberman

if node.chef_environment != 'development'

  cookbooks = {}
  node.cookbook_collection.values.each {|c| cookbooks[c.name.to_s] = c.version.to_s }

  # See https://github.com/danryan/spice
  r = gem_package "spice" do
    version "0.8.0"
  end
  r.run_action(:install)

paulmillr

Most active GitHub users (git.io/top)

The count of contributions (summary of Pull Requests, opened issues and commits) to public repos at GitHub.com from Wed, 21 Sep 2022 till Thu, 21 Sep 2023.

Only first 1000 GitHub users according to the count of followers are taken. This is because of limitations of GitHub search. Sorting algo in pseudocode:

githubUsers
 .filter(user => user.followers > 1000)