<commit_before>Title: Getting started... :  Wheat setup, part 2
Author: <NAME>
Date: Apr 3 2013 17:30:00 GMT-0500 (CST)
Categories: node,blog,wheat,ec2,aws
Email: <EMAIL>

In this article I'll run through the setup of this blog on an ec2 instance with a cheap dns entry.

## PaaS

I've seen a number of articles on the use of various PaaS and spent some time, about an hour
each, reviewing them.  Ultimately, for my purposes I just directly provisioned an ec2 micro instance and within about
an hour had it updated and everything installed.  This may not be a fair assessment for other people as I had previously
spent a significant amount of time previously learning how to use the aws cli and had some simple shell scripts for
quickly setting up an instance.

I'm sure the provisioning and setup for some, most or all of these is simpler than


 - Cloudfoundry
 - Openshift
 - Heroku
 - Nodejitsu
 - Openshift
 - Vagrant

To be fair it's a single instance and I didn't attach an EBS to it so that if it crashes I'll will have to manually
intervene.

## Provisioning

## Security Groups

## Installation

## HTTP & HTTPS

## Starting The Server<commit_msg>article updates<commit_after>Title: Getting started... :  Wheat setup, part 2
Author: <NAME>
Date: Apr 3 2013 17:30:00 GMT-0500 (CST)
Categories: node,blog,wheat,ec2,aws
Email: <EMAIL>

In this article I'll run through the setup of this blog on an ec2 instance with a cheap dns entry.

## PaaS

I've seen a number of articles on the use of various PaaS and spent some time, about an hour
each, reviewing them.  Ultimately, for my purposes I just directly provisioned an ec2 micro instance and within about
an hour had it updated and everything installed.  This may not be a fair assessment for other people as I had previously
spent a significant amount of time previously learning how to use the aws cli and had some simple shell scripts for
quickly setting up an instance.

I'm sure the provisioning and setup for some, most or all of these is simpler than


 - [Cloudfoundry](http://cloudfoundry.com)
 - [Heroku](http://heroku.com)
 - [Nodejitsu](http://nodejitsu.com)
    It's important to know that nodejitsu only allows port 80.  Great security, but a little lacking in flexibility
 - [Openshift](http://openshift.com)
 - [Vagrant](http://vagrant.com)

To be fair it's a single instance and I didn't attach an EBS to it so that if it crashes I'll will have to manually
intervene.

## Provisioning

## Security Groups

## Installation

## HTTP & HTTPS

## Starting The Server
{'fraction_non_alphanumeric': 0.06385494678754434, 'fraction_numerical': 0.015766653527788728, 'mean_word_length': 4.065868263473054, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1682417', 'n_tokens_mistral': 776, 'n_tokens_neox': 716, 'n_words': 383}