This gist assumes:
www-data (may be apache on other systems)
| #Author: Jacob Rust | |
| #Date: 7/8/2013 | |
| #Description:This script organizes downloaded files into separate folders depending | |
| #on the file type. This was made for windows systems. | |
| #Download directory should be the first command line argument | |
| #New file types can be added to the dictionary in the main method | |
| import os | |
| import sys | |
| import hashlib |
This is a description of how I write tech articles for various blogs. Hopefully someone else will find this useful as well.
When I begin writing a new article, I create a new [GitHub Gist][gist] for the article files. The Gist contains a file for the article text and code examples related to the article.
DevOps started out as "Agile Systems Administration". In 2008, Andrew Shafer did a talk called "Agile Infrastucture" addressing issues around involving more of the company in the same disciplines as programmers.
In 2009, Patrick Debois created "DevOpsDays" conference to help to bring it to light. However, it wouldn't begin to trend until about 2010, when people would begin to describe it as a standalone discipline.
Today, DevOps goes beyond just developers, systems administration and infrastructure, its about [dev, ops, agile, cloud, open source and business](https://blogs.the451group.com/opensource/2010/03/03/devops-mixing-dev-ops-agile-cloud-open-source-and-busi
DevOps started out as "Agile Systems Administration". In 2008, Andrew Shafer did a talk called "Agile Infrastucture" addressing issues around involving more of the company in the same disciplines as programmers.
In 2009, Patrick Debois created "DevOpsDays" conference to help to bring it to light. However, it wouldn't begin to trend until about 2010, when people would begin to describe it as a standalone discipline.
Today, DevOps goes beyond just developers, systems administration and infrastructure, its about [dev, ops, agile, cloud, open source and business](https://blogs.the451group.com/opensource/2010/03/03/devops-mixing-dev-ops-agile-cloud-open-source-and-busi
| git clone https://github.com/vfarcic/k8s-specs.git | |
| cd k8s-specs | |
| git pull | |
| open "https://console.aws.amazon.com/iam/home#/security_credential" | |
| export AWS_ACCESS_KEY_ID=[...] |
Create the appropriate VPC that your application is going to live in. Create subnets for each availability zone you want to use.
Create VPC security group(s) for your auto-scaling instances. For example, if you're going to auto-scale web servers, create a "web" VPC security group.
Go into AWS console and create an ELB. Easy wizard. Select HTTP and (if needed) HTTPS. Make sure it's associated with the VPC you created in step 1.
Create an auto-scaling launch configuration from the CLI. The launch configuration has the AMI, size, and security group from step #2. The security group must be by ID not name ("sg-12345"):
as-create-launch-config web --image-id ami-2e31bf1e --instance-type m1.medium \
-g sg-7619041a --key root
Create the appropriate VPC that your application is going to live in. Create subnets for each availability zone you want to use.
Create VPC security group(s) for your auto-scaling instances. For example, if you're going to auto-scale web servers, create a "web" VPC security group.
Go into AWS console and create an ELB. Easy wizard. Select HTTP and (if needed) HTTPS. Make sure it's associated with the VPC you created in step 1.
Create an auto-scaling launch configuration from the CLI. The launch configuration has the AMI, size, and security group from step #2. The security group must be by ID not name ("sg-12345"):
as-create-launch-config web --image-id ami-2e31bf1e --instance-type m1.medium \
-g sg-7619041a --key root