byplayer

export GIT_SSL_NO_VERIFY=true                          

CristinaSolana

1. Clone your fork:

git clone git@github.com:YOUR-USERNAME/YOUR-FORKED-REPO.git

2. Add remote from original repository in your forked repository:

cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream

DavidWittman

A Brief Introduction to Fabric

Fabric is a deployment management framework written in Python which makes remotely managing multiple servers incredibly easy. If you've ever had to issue a change to a group servers, this should look pretty familiar:

for s in $(cat servers.txt); do ssh $s service httpd graceful; done

Fabric improves on this process by providing a suite of functions to run commands on the servers, as well as a number of other features which just aren't possible in a simple for loop. While a working knowledge of Python is helpful when using Fabric, it certainly isn't necessary. This tutorial will cover the steps necessary to get started with the framework and introduce how it can be used to improve on administering groups of servers.

lavoiesl

<VirtualHost *:80>
  ServerAdmin {USER}@cslavoie.com
  ServerName {DOMAIN}
  ServerAlias www.{DOMAIN}
  ServerAlias {USER}.localhost
  ServerAlias {USER}.static.cslavoie.com

  DocumentRoot {DOC_ROOT}

  <Directory {DOC_ROOT}>

lukaslundgren

sudo apt-get install build-essential libsqlite3-dev zlib1g-dev libncurses5-dev libgdbm-dev libbz2-dev libreadline5-dev libssl-dev libdb-dev

wget http://www.python.org/ftp/python/2.7.3/Python-2.7.3.tgz
tar -xzf Python-2.7.3.tgz
cd Python-2.7.3

./configure --prefix=/usr --enable-shared
make
sudo make install
cd ..

andreicristianpetcu

An Ansible summary

Jon Warbrick, July 2014, V3.2 (for Ansible 1.7)

Configuration file

intro_configuration.html

First one found from of

leonardofed

A curated list of AWS resources to prepare for the AWS Certifications

A curated list of awesome AWS resources you need to prepare for the all 5 AWS Certifications. This gist will include: open source repos, blogs & blogposts, ebooks, PDF, whitepapers, video courses, free lecture, slides, sample test and many other resources.

---

dmerrick

#!/usr/bin/env ruby
# this script will delete ECR images that are older than N days

require 'date'
require 'json'

# customize this script
repo = 'snapdocs'
delete_if_older_than = 60 # days

jpierson

If you are like me you find yourself cloning a repo, making some proposed changes and then deciding to later contributing back using the GitHub Flow convention. Below is a set of instructions I've developed for myself on how to deal with this scenario and an explanation of why it matters based on jagregory's gist.

To follow GitHub flow you should really have created a fork initially as a public representation of the forked repository and the clone that instead. My understanding is that the typical setup would have your local repository pointing to your fork as origin and the original forked repository as upstream so that you can use these keywords in other git commands.

1. Clone some repo (you've probably already done this step)

   git clone git@github...some-repo.git

pareddy113

----- Interested Reads------
+ Interesting Read (Serverless Architecture of Acloud guru)
  https://read.acloud.guru/serverless-the-future-of-software-architecture-d4473ffed864
  
----- Getting Started-------
+ Requirements 
  + AWS Free Tier Account
  + PC with putty and putty keygen/ Mac
  + Optional
    + IoS/ Android App $20