Visual Studio 2012 Using a git Repository

Posted on Thursday, April 25, 2013




I have recently been working on a project using C# and .Net.  I decided to go ahead and buy Visual Studio 2012 Professional.  So far I like it but I have not had time yet to set up a proper repository for it.   I was planning on using git, but I figured Microsoft would not support it directly and I would be forced to use git on the command line (which I am fine with).  Well it turns out Visual Studio 2012 does support git.

I found some information on the fact that Visual Studio can use git at this site. http://www.hanselman.com/blog/GitSupportForVisualStudioGitTFSAndVSPutIntoContext.aspx [1]


This document does not go over TFS (Team Foundation Server), although you can use git with TFS.  Also you can use git with  Team Foundation Service https://tfs.visualstudio.com/en-us/, its free for up to 5 users (not sure if it's going to remain that way)

Copy AMI Between Regions

Posted on Sunday, April 21, 2013



On March 13th 2013 Amazon AWS announced a new AMI copy tool to copy images between regions.  They also posted a how to guide on how to use it at http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/CopyingAMIs.html?ref_=pe_12300_28673600_7 [1]


This I my simple guide on how to do it (it is very easy)


Amazon AWS Fix cloud-init in Ubuntu 12.10

Posted on Monday, April 15, 2013



This guide goes over fixing one bug in the cloud-init feature in Ubuntu 12.10.  The issue is this, when creating a user and giving them a password their password becomes "locked"


In the cloud-init version 0.7 installed with Ubuntu 12.10 AMIs there is a bug if you are trying to set the password for a user it becomes locked.   
The bug and its fix are covered here https://bugs.launchpad.net/cloud-init/+bug/1096423 [1]  So it has been fixed but the fix is not on the Ubuntu 12.10 AMI images yet (And I do not think it ever will be).   So here is my process for putting this fix into a 12.10 AMI and making your own AMI to use.


(4 of 4) Amazon ELB Multi-domain SSL forwarding to NGINX and Play Servers

Posted on Wednesday, April 10, 2013




(4 of 4  Create an ELB with the signed certificate)

This guide goes over setting up an ELB with a multi-domain SSL certificate.  The servers attached to the ELB will run multiple Play servers on different ports with an nginx server running in front of them to handle routing based on domain/subdomain names.

I know that is quite a mouthful but here is what I am trying to accomplish….

I want to run more than one Play Server on an ec2 instance.  Each Play Server will run on its own port.   I want to have a domain name to route to a specific Play server.  Ex.  www.example.com routes to the Play server running on port 9000 and  www2.example.com routes to the Play server running on port 8000.   In addition I want all the communication to be secure using ssl certificates.

For an individual server you could simply put a nginx server in front of the Play servers and have the nginx handle routing based on domain name.  But, in this case I want to add an AWS ELB (Elastic Load Balancer) in front of several EC2 machines.

Here is what I have found out thus far.   The ELB can handle the ssl certificate, but it can only have one certificate per ELB.  This forces you to use a multi-domain SSL certificate.   Also the ELB cannot port forward based on domain name so you still need an nginx server in front of the Play servers.




I want something like this.  The ELB handles the certificate and the nginx server handles the domain name routing.

(3 of 4) Amazon ELB Multi-domain SSL forwarding to NGINX and Play Servers



(3 of 4  Signed Multi-domain ssl certificate from godaddy)

This guide goes over setting up an ELB with a multi-domain SSL certificate.  The servers attached to the ELB will run multiple Play servers on different ports with an nginx server running in front of them to handle routing based on domain/subdomain names.

I know that is quite a mouthful but here is what I am trying to accomplish….

I want to run more than one Play Server on an ec2 instance.  Each Play Server will run on its own port.   I want to have a domain name to route to a specific Play server.  Ex.  www.example.com routes to the Play server running on port 9000 and  www2.example.com routes to the Play server running on port 8000.   In addition I want all the communication to be secure using ssl certificates.

For an individual server you could simply put a nginx server in front of the Play servers and have the nginx handle routing based on domain name.  But, in this case I want to add an AWS ELB (Elastic Load Balancer) in front of several EC2 machines.

Here is what I have found out thus far.   The ELB can handle the ssl certificate, but it can only have one certificate per ELB.  This forces you to use a multi-domain SSL certificate.   Also the ELB cannot port forward based on domain name so you still need an nginx server in front of the Play servers.




I want something like this.  The ELB handles the certificate and the nginx server handles the domain name routing.


(2 of 4) Amazon ELB Multi-domain SSL forwarding to NGINX and Play Servers



(2 of 4  Install nginx server)

This guide goes over setting up an ELB with a multi-domain SSL certificate.  The servers attached to the ELB will run multiple Play servers on different ports with an nginx server running in front of them to handle routing based on domain/subdomain names.

I know that is quite a mouthful but here is what I am trying to accomplish….

I want to run more than one Play Server on an ec2 instance.  Each Play Server will run on its own port.   I want to have a domain name to route to a specific Play server.  Ex.  www.example.com routes to the Play server running on port 9000 and  www2.example.com routes to the Play server running on port 8000.   In addition I want all the communication to be secure using ssl certificates.

For an individual server you could simply put a nginx server in front of the Play servers and have the nginx handle routing based on domain name.  But, in this case I want to add an AWS ELB (Elastic Load Balancer) in front of several EC2 machines.

Here is what I have found out thus far.   The ELB can handle the ssl certificate, but it can only have one certificate per ELB.  This forces you to use a multi-domain SSL certificate.   Also the ELB cannot port forward based on domain name so you still need an nginx server in front of the Play servers.




I want something like this.  The ELB handles the certificate and the nginx server handles the domain name routing.


(1 of 4) Amazon ELB Multi-domain SSL forwarding to NGINX and Play Servers



(1 of 4  Install Scala and Play on Ubuntu 12.10)

This guide goes over setting up an ELB with a multi-domain SSL certificate.  The servers attached to the ELB will run multiple Play servers on different ports with an nginx server running in front of them to handle routing based on domain/subdomain names.

I know that is quite a mouthful but here is what I am trying to accomplish….

I want to run more than one Play Server on an ec2 instance.  Each Play Server will run on its own port.   I want to have a domain name to route to a specific Play server.  Ex.  www.example.com routes to the Play server running on port 9000 and  www2.example.com routes to the Play server running on port 8000.   In addition I want all the communication to be secure using ssl certificates.

For an individual server you could simply put a nginx server in front of the Play servers and have the nginx handle routing based on domain name.  But, in this case I want to add an AWS ELB (Elastic Load Balancer) in front of several EC2 machines.

Here is what I have found out thus far.   The ELB can handle the ssl certificate, but it can only have one certificate per ELB.  This forces you to use a multi-domain SSL certificate.   Also the ELB cannot port forward based on domain name so you still need an nginx server in front of the Play servers.




I want something like this.  The ELB handles the certificate and the nginx server handles the domain name routing.


Amazon AWS ELB using VPC with SSL

Posted on Sunday, April 7, 2013



This guide goes through the setup of an ELB (Elastic load balancer in the AWS amazon cloud) with an SSL certificate.

For this test I am going to set up an ec2 instance with Ubuntu 12.10 running an nginx server.


Installing AWS IAM command line tools in Ubuntu

Posted on Friday, April 5, 2013



This guide goes over setting up the amazon AWS IAM (Identity and Access Management) command line tools.

I had to recently set these up due to a tool missing from the aws web console  (well maybe it's there but I can't seem to find it)  I recently added an SSL certificate to an ELB as a test.  The SSL certificate is somehow stored within the IAM system.   The only way I can see to remove the SSL certificate is to use the IAM command line tools.