sqlup 0.0.1 → 0.0.2

data/README.txt

@@ -1,5 +1,6 @@
-sqldump
+sqlup
     by James Moore
+    http://sqlup.restphone.com
 
 == DESCRIPTION:
 
@@ -34,7 +35,7 @@ Retrieve the backup files (where full:type_mysqldump:log_file_domU-12-31-35-00-3
 === Usage
 
 Get help:
-  sqlup �h 
+  sqlup -h 
 Back up the data files: 
   sqlup binary -bucket sqlup
 Back up a mysqldump run: 
@@ -58,8 +59,8 @@ You need to specify your access codes using the AWS::S3 environment variables:
   export AMAZON_SECRET_ACCESS_KEY='xxxxxxxxxx'
 
   
-It�s primarily targeted at MySQL servers running on Amazon�s EC2 virtual server system,
-with backups sent to Amazon�s S3 storage service.
+It's primarily targeted at MySQL servers running on Amazon's EC2 virtual server system,
+with backups sent to Amazon's S3 storage service.
 
 === What it backs up
 There are three parts to a MySQL backup system:
@@ -68,22 +69,22 @@ There are three parts to a MySQL backup system:
 2.	Full dumps using the mysqldump tool.
 3.	The binary log files.
 
-Normally, you�d make a full copy of your system using either #1 or #2, and then have sqlup make backups of the binary logs to S3 every N seconds.
-Backups are tarred, gzip�ed, and split to fit into S3 buckets.
+Normally, you'd make a full copy of your system using either #1 or #2, and then have sqlup make backups of the binary logs to S3 every N seconds.
+Backups are tarred, gzip'ed, and split to fit into S3 buckets.
 
 === FAQs
 
 *  Why would I want to make copies of the data files instead of using mysqldump?
 
-Speed.  Recovering mysqldump files can take a while; recovering when you have copies of the data files is much faster.  If you�ve got a small database, though, just use mysqldump.  You can test this yourself; just do a mysqldump of your current database, and run it against a MySQL server on another machine.  If that�s fast enough for you, you don�t need to worry about the binary files.
+Speed.  Recovering mysqldump files can take a while; recovering when you have copies of the data files is much faster.  If you've got a small database, though, just use mysqldump.  You can test this yourself; just do a mysqldump of your current database, and run it against a MySQL server on another machine.  If that's fast enough for you, you don't need to worry about the binary files.
 
-* Can I use the database while it�s being backed up?
+* Can I use the database while it's being backed up?
 
-Yes, sort of.  The binary backup is going to lock every table in the system until it�s finished making a tarball of all the data files.  (A future enhancement will be to use a versioning file system.)  As long as no one writes to the database, reads will continue.  However, as soon as someone wants to write to a table, it�s very likely that all future readers will be blocked until the backup is finished writing temporary files to disk.
+Yes, sort of.  The binary backup is going to lock every table in the system until it's finished making a tarball of all the data files.  (A future enhancement will be to use a versioning file system.)  As long as no one writes to the database, reads will continue.  However, as soon as someone wants to write to a table, it's very likely that all future readers will be blocked until the backup is finished writing temporary files to disk.
 
 * Is there an automated recovery system?
 
-Not yet.  There�s a command to get the backups back from S3, but you need to go through the standard mysql recovery process by hand once you have the files.
+Not yet.  There's a command to get the backups back from S3, but you need to go through the standard mysql recovery process by hand once you have the files.
 
 
 == FEATURES/PROBLEMS:
@@ -119,4 +120,4 @@ GNU General Public License for more details.
 
 You should have received a copy of the GNU General Public License
 along with this program; if not, write to the Free Software
-Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.
+Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.

data/bin/sqlup

@@ -15,7 +15,8 @@ module Example extend OptiFlagSet
   keyword 'get', :description => 'Get a binary or a mysqldump backup.  Requires --name'
   keyword 'get_logs', :description => "Get all the current and complete logs"
   keyword 'rm', :description => 'Remove a backup (use -name to specify which backup to remove)'
-  flag 'bucket', :description => "The name of the S3 bucket"
+  keyword 'help'
+  optional_flag 'bucket', :description => "The name of the S3 bucket"
   optional_flag 'backup_type', :description => "(ls) The kind of backup"
   optional_flag 'skip_most_recent', :description => "(ls) Do not display the most recent N logs.  Usually used to get a list of obsolete current logs."
   optional_flag 'name', :description => '(get, rm) The name of the backup to process'
@@ -30,6 +31,13 @@ end
 
 flags = ARGV.flags
 
+if flags.help?
+  puts File.readlines(File.dirname(__FILE__) + '/../README.txt')
+  exit 0
+end
+
+puts "Warning: no -bucket specified" unless flags.bucket?
+
 if flags.get && !flags.name
   raise RuntimeError, "You must specify the name of a backup (--name)"
 end

data/lib/mysql_backup.rb

@@ -4,5 +4,5 @@ require 'mysql_backup/librarian'
 require 'mysql_backup/storage/s3'
 
 module MysqlBackup
-  VERSION = '0.0.1'
+  VERSION = '0.0.2'
 end

metadata

@@ -3,8 +3,8 @@ rubygems_version: 0.9.4
 specification_version: 1
 name: sqlup
 version: !ruby/object:Gem::Version 
-  version: 0.0.1
-date: 2007-06-22 00:00:00 -07:00
+  version: 0.0.2
+date: 2007-06-23 00:00:00 -07:00
 summary: A backup tool for saving MySQL data to Amazon's S3 service
 require_paths: 
 - lib