whatupfoo

Organization archetypes

The intention of this document is to provide some guidance and suggestions to customers who are wondering how they should structure organizations and teams in their GitHub Enterprise environment. The idea isn't to give hard and fast rules on which approach is better than the other, but to give examples of when one approach might be preferable to another depending on the use case.

1. A single organization with direct organization membership for repository access (not teams)

          ________________
          |     Org      |
          |    ______    |
          |   |      |\  |

| | Repo | \ |

whatupfoo

#!/usr/bin/env ruby

# frozen_string_literal: true

require "csv"
require "jwt"
require "octokit"
require "optparse"
require "spreadsheet"
require "yaml"

whatupfoo

aws elb describe-load-balancers --load-balancer-name [elb-name]

aws elb create-load-balancer-policy --load-balancer-name [elb-name] --policy-name my-ProxyProtocol-policy --policy-type-name ProxyProtocolPolicyType --policy-attributes AttributeName=ProxyProtocol,AttributeValue=true

aws elb set-load-balancer-policies-for-backend-server --load-balancer-name [elb-name] --instance-port 23 --policy-names my-ProxyProtocol-policy

aws elb set-load-balancer-policies-for-backend-server --load-balancer-name [elb-name] --instance-port 81 --policy-names my-ProxyProtocol-policy

aws elb set-load-balancer-policies-for-backend-server --load-balancer-name [elb-name] --instance-port 444 --policy-names my-ProxyProtocol-policy