CODEWITHSUNDEEP
testingamazon-ec2synchronizationsetup-deploymentprototyping
user762391
user762391

Reputation:

Prototyping for Amazon EC2

I wonder how people are prototyping for EC2.

In my case i want to code locally in my preferred editor and sync to a test instance and debug there, is this common practice? (vi/vim over ssh is not an option)

If so, are there any tools to sync code locally with a test instance other than rsync/sftp, anything automated?

If not, what are the options?

Any tips/walkthrough of how your code/debug cycle for EC2 looks like (pre commit), are appreciated.

Upvotes: 0

Views: 109

Answers (2)

Eric J.
Eric J.

Reputation: 150148

My preferred setup is to

  • Code on a local machine
  • Check into version control
  • Use continuous automation to get the checkins to version control and create a build
  • Push the build result to a QA (or prototyping in your case) instance on EC2 (I used Maven, you could use FTP or rsync).
  • When the QA (or prototyping) box is doing what you want, create an AMI of it. Use that AMI to launch production instances.

Upvotes: 3

Mike Brant
Mike Brant

Reputation: 71414

Revision control is your friend. Make you local code changes, submit them to your revision control server, then pull the changes into you amazon instance.

Upvotes: 1

Related Questions