binford2k

  # Make sure that all channels are subscribed to before any packages are installed.
  # This is evil and horrible and not right. But it's really the only way right now.
  # TODO: use a whit to coalesce relationships for performance reasons. This won't
  #       really matter until you have many channels subscribed.
  def autorequire(rel_catalog = nil)
    rel_catalog ||= catalog
    raise(Puppet::DevError, "You cannot add relationship without a catalog") unless rel_catalog

    reqs = super
    rel_catalog.resources.select{|x| x.is_a? Puppet::Type::Package}.each do |res|

christiangenco

require 'http'
require 'json'
require 'peach'
require 'gabbler'
require 'pry'

USERNAME = "patio11"

unless File.exists?("comments.txt")
  def get_json(url)

bewest

metaenvdir server

Unique environment for same server.

awaxa

---
sockets:
  - id: 'one'
    address: '127.0.0.1'
    port: '8001'
  - id: 'two'
    address: '127.0.0.2'
    port: '8002'

tsiege

ANNOUNCEMENT

I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!






\

willurd

Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.

Discussion on reddit.

Python 2.x

$ python -m SimpleHTTPServer 8000

bernd

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = [email protected]:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

ahpook

I feel your pain. SSL is tough and is probably the number one stumbling block for new users getting Puppet working in their environment. Hopefully this answer helps reduce frustration and get you up and running. The good news is, once it's set up right, you won't have to fiddle with it any more.

First, make sure the problem you're having is actually an SSL problem. Almost all of the SSL-related error messages on the client start with the string SSL_connect and then the error raised up by the underlying crypto libraries. General networking errors will not have this string, so normal network troubleshooting methodology applies; specifically, Connection refused - connect(2) means a TCP connection attempt got a RST packet indicating a firewall or puppet master not running, and getaddrinfo: nodename nor servname provided, or not known means the server's hostname (the value of puppet agent --configprint server) was not resolvable in DNS/hosts.

Next, assuming you do have an SSL_connect style error, it