mmarschall / s3db-backup Goto Github PK

s3db-backup <= 0.6.4 is basically a set of ruby scripts with lots of duplication. Even worse, it does not have a single test. This makes changing the code very hard and dangerous.

s3db-backup should be fully tested with rspec and should be separated into maintainable ruby classes to simplify further development.

We need to be able to select a specific section in database.yml instead of only setting the db name

It should not necessarily run with every load and it should have a proper hook instead of living in S3DbBackup class.

s3db:latest:load always tries to load the mysql dump into a database on localhost.

It does not use the host given in database.yml

s3db should use the host from database.yml if defined, otherwise default to localhost

Currently s3db:latest:load tries to recreate the database. This fails if the database is not (yet) existing.

It should work no matter whether the database exists or not.

DB backup functionality is working fine in staging environment. But when im trying to invoke the rake task to upload the db to s3...git stuck by getting the following error..

"mysqldump: Got error: 1045: Access denied for user 'dbname'@'server private ip address' (using password: YES) when trying to connect"

Im wondering why it would take server instead of host address from database.yml

I have also declared config variables in application.rb,
ENV['S3DB_BUCKET'] = "XXXXXXXX"
ENV['S3DB_DATABASE_CONFIG'] = "production"

I would appreciate if you can assist me in fixing this issue.

Thanks.
Amit

While the backup and restore run nicely under Rails 3, the generator, which helps to setup the config files, does not yet run under Rails 3.

There should be a built in way to get automatically get rid of old backups e.g. keep only last X backups

is the 0.8.2 discontinued now ?
im getting this error
Could not find s3db-backup-0.8.2 in any of the sources

In 0.6.4 the load task is unzipping the dump. Because of that you can't run load twice without either fetching the dump again or zipping it manually before running load.

The dump should be unzipped by fetch instead. That way we can run load multiple times on the same dump without manual intervention.

Right now s3db-backup is hard wired to right_aws gem. It should be possible to use other providers, especially fog.

I've removed the rails_env attribute from the S3DbBackup class.

If you want to change the database to load into, there is no way to do so right now. We need a way to be able to configure the target database.

s3db_backup is supporting a bunch of environment variables to tweak how it works. They need to be documented in the README.rdoc

S3DB_BUCKET
S3DB_SECRET_KEY_PATH
S3DB_DATABASE_CONFIG

Right now, ccrypt is hard wired. It should be possible to use any other (maybe already installed tool).

backup currently ignores the port.

It should add --port=XXXX to the mysqldump command.

Right now, s3db is hard wired to use gzip. It should be possible to use e.g. bzip2 as well.

right_aws seems to break some weird stuff with UTF-8 characters on the wire.