launchpad development|
⇤ ← Revision 1 as of 2012-10-30 11:58:05
Size: 1024
Comment:
|
Size: 1061
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
Notes: * AMI ID: ami-372d0b72 |
|
| Line 7: | Line 11: |
| 3. Launch as many instances of the API as you need, using your default AWS keypair and the security group you created above. | 3. Launch as many instances of the AMI as you need, using your default AWS keypair and the security group you created above. |
Launchpad Clinics - EC2 Machines
Notes:
- AMI ID: ami-372d0b72
Instructions for set-up
Get gmb to add your AWS Account Number (see https://portal.aws.amazon.com/gp/aws/manageYourAccount) to the AMI for the LP clinics.
- Create a security group for the instances of this AMI, allowing incoming traffic on ports 22, 80 and 443.
- Launch as many instances of the AMI as you need, using your default AWS keypair and the security group you created above.
When someone wants to use a machine, log into that machine using ssh -i /path/to/keypair ubuntu@machine.aws.address and run the following: get-lp-ssh-keys $lpname >> .ssh/authorized_keys where $lpname is the LP username of the person who's going to be hacking on that machine.
- Have the user log into the machine and run the following:
$ cd launchpad $ ./rocketfuel-setup
The machine is now ready to use. The user should also generate an SSH key (ssh-keygen) and upload it to Launchpad so that they'll be able to push any code they commit.
