Also on twitter ( twitter.com/nutrun )
«
»

rubyworks-ec2 0.1.3

George Malamidis, December 10th, 2007

New in version 0.1.3 of rubyworks-ec2:

Added db:list_backups task for displaying a list of all S3 MySQL backups.

The db:restore task now accepts an optional VERSION argument for restoring the instance’s database to the specified revision. If VERSION is omitted the task defaults to the latest backup found on S3. For example: 

cap db:list_backsups

mysql-backup-1197246181
mysql-backup-1197318602
mysql-backup-1197318629
mysql-backup-1197318764

cap db:restore VERSION=1197318629

Fixed a bug on the image:backup task. Thanks to Nick Kallen for noticing and reporting this.

The following needs to be set in deploy.rb in order for the image:backup task to work properly: 

set :bucket, "name-the-bucket-that-will-hold-the-image"

This entry was posted on Monday, December 10th, 2007 at 10:50 pm and is filed under Software. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

4 Responses to “rubyworks-ec2 0.1.3”

  1. ThomasB Says:
    December 14th, 2007 at 1:49 pm

    Amazon SimpleDB was announced today. Is this a natural replacement for the S3 backup of the mysql db in rubyworks-ec2 ? Or do you see SimpleDB as something that every developer must implement in their rails apps as seen fit instead ?

  2. George Malamidis Says:
    December 14th, 2007 at 7:23 pm

    Thomas,

    At the moment, S3 seems to be the right tool for the job when it comes to backing up and restoring the database. SimpleDB definitely looks like something worth investigating, but I’m not sure whether it’s more appropriate than S3 for something as simple as database back ups.

  3. Ram Says:
    January 7th, 2008 at 2:04 pm

    Hey,

    Thanks for this gem.

    Does this support the “large” and the “extra large” instance in amazon?

    Also,how can we change the number of mongrel instances?

    Any other tuning that you think would be useful?

    Thanks,

  4. George Malamidis Says:
    January 12th, 2008 at 2:43 am

    Ram,

    I haven’t tried the gem with L or XL instances, but I don’t see why it would make a difference.

    Try “ec2run ami-30f11459 –instance-type m1.xlarge -k <keypair>”, get the instance id once the instance starts and then do “cap instance:bootstrap”…

    You will have to remotely connect to the instance to change the number of mongrels.

    “cap instace:ssh”

    Monit and Mongrel configurations can be found in “/etc/rails”. SV configs for Mongrels are in “/var/service”

    Once you’re happy with your configuration, invoke “cap mongrel stop”, “cap monit:restart” and “cap mongrel:start” from your application’s capified directory.

    “cap monit status” will display some useful info on the Mongrel instances.

Leave a Reply