Re: [development] Database Administrator
Sime: I contacted him and he replied at first instantenousely then I sent him more info about my module but he didn't reply for about 10 days. Kieran: 1. I won't release until I get a reply from Jeremy. 2. I have some features like: -- scheduled backups -- you can define multiple backup locations like: -- have them sent to your e-mail -- mirror your db to another mysql server to a specific db or create a new db for every backup -- stored on remote FTP -- a folder under files/ in your drupal -- you can have the module trying all possible locations until successful or have it sending the backup to all locations -- you can maintain a certain count of backups and I donno whether database admin module is offering those features. Awaiting your feedback.
On Nov 16, 2006, at 7:59 AM, Omar Abdel-Wahab wrote:
Sime: I contacted him and he replied at first instantenousely then I sent him more info about my module but he didn't reply for about 10 days.
Kieran: 1. I won't release until I get a reply from Jeremy. 2. I have some features like: -- scheduled backups -- you can define multiple backup locations like: -- have them sent to your e-mail -- mirror your db to another mysql server to a specific db or create a new db for every backup -- stored on remote FTP -- a folder under files/ in your drupal -- you can have the module trying all possible locations until successful or have it sending the backup to all locations -- you can maintain a certain count of backups and I donno whether database admin module is offering those features.
Awaiting your feedback.
Sounds great. Perhaps you could put a version in your sandbox for people to try out. Cheers, Kieran
Omar, Does your module support PostgreSQL - the better DBMS? -- Sammy Spets Synerger Pty Ltd http://synerger.com On 16-Nov-06 17:59, Omar Abdel-Wahab wrote:
Sime: I contacted him and he replied at first instantenousely then I sent him more info about my module but he didn't reply for about 10 days.
Kieran: 1. I won't release until I get a reply from Jeremy. 2. I have some features like: -- scheduled backups -- you can define multiple backup locations like: -- have them sent to your e-mail -- mirror your db to another mysql server to a specific db or create a new db for every backup -- stored on remote FTP -- a folder under files/ in your drupal -- you can have the module trying all possible locations until successful or have it sending the backup to all locations -- you can maintain a certain count of backups and I donno whether database admin module is offering those features.
Awaiting your feedback.
Hi Omar, This sounds nice. You might also find some good info on http:// cvs.drupal.org/viewcvs/drupal/contributions/modules/fbu/ which is a file backup module by Robert Douglass. We were going to do some things w/ FBU back in March but did not get around to it. It has some pear package dependencies. (side note - then again i think there's a module to let you add pear package support to drupal w/o needing to install on server itself.) I think the idea of FBU is for backing up the /files/ directory which has the potential for lots of new data on daily basis. What if dbbackup could write to something in /files/dbbackup/ (and maybe rotate out every week or X number days so you can keep a week's worth of dbbackups locally, and then you have the module let you backup /files/ and send it off to email/ftp/etc.? I think this can be pretty valuable, esp. for where you don't have backup routines setup server-wide (like w/ shared hosting) as well as you could do one-click on-demand button to backup your entire site, if you're about to try/test something :) sounds very handy. On Nov 16, 2006, at 10:59 AM, Omar Abdel-Wahab wrote:
2. I have some features like: -- scheduled backups -- you can define multiple backup locations like: -- have them sent to your e-mail -- mirror your db to another mysql server to a specific db or create a new db for every backup -- stored on remote FTP -- a folder under files/ in your drupal
Ian Ward Development Seed Inc. Technology Development and Discovery http://www.developmentseed.org http://www.developmentseed.org/blog developmentseedperu(skype) Tel. 202.250.3633 Fax. 806.214.6218
On Nov 16, 2006, at 7:59 AM, Omar Abdel-Wahab wrote:
1. I won't release until I get a reply from Jeremy.
i'm co-maintaining dba.module. sadly, i've been way too busy working on the release system to give it any love in many months.
2. I have some features like: -- scheduled backups
dba does this. it also has a nice feature i added to let you exclude certain tables, so you don't dumb the cache, search index, watchdog, etc into your backups if you don't want them (it exports the table definition, just not the data, so you can still load these backups into a new DB and have a working system).
-- you can define multiple backup locations like: -- have them sent to your e-mail
dba does this.
-- mirror your db to another mysql server to a specific db or create a new db for every backup
this would be new.
-- stored on remote FTP -- a folder under files/ in your drupal
evil security hole unless you lock down this directory via .htaccess. dba does allow you to store to a local directory of your choice, and encourages you to do it *NOT* under /drupal. ;)
-- you can have the module trying all possible locations until successful or have it sending the backup to all locations
would be new.
-- you can maintain a certain count of backups
would be new.
and I donno whether database admin module is offering those features.
now you know. ;) ultimately, no one can stop you, but i'd be *VERY* opposed to adding a different module for scheduled backups. dba.module does *so* much more than just the backups, and should be The One True(tm) solution for all such things in Drupal. the HEAD version kinda works in 4.7.x right now, so you can poke around with it and see what's possible, even if not everything works properly. ;) there are already a handful of issues in the dba queue for porting to 4.7. jeremy basically halted all work on this module, i've been too busy working on the release system, and no one else has stepped up. i'd *LOVE* it if you took up the torch on this, and started to: a) submitted patches for those 4.7.x porting issues so we can add a DRUPAL-4-7 branch b) rolled your new functionality into patches so we can make a DRUPAL-4-7--2 branch c) began submitting patches for porting to 5.x. if you do, i promise i'll be ultra responsive with reviews, commits, and when appropriate, branches and releases. i might even be able to do some of the work myself, depending on whatever else comes up in the next few weeks. thanks! -derek
Just to add to what Derek has written, I sorely miss a stable dba in 4-7. It's a great module and should get some loving. -Robert Derek Wright wrote:
i'd *LOVE* it if you took up the torch on this, and started to:
a) submitted patches for those 4.7.x porting issues so we can add a DRUPAL-4-7 branch b) rolled your new functionality into patches so we can make a DRUPAL-4-7--2 branch c) began submitting patches for porting to 5.x.
if you do, i promise i'll be ultra responsive with reviews, commits, and when appropriate, branches and releases. i might even be able to do some of the work myself, depending on whatever else comes up in the next few weeks.
thanks! -derek
On Nov 16, 2006, at 11:51 AM, Derek Wright wrote:
a) submitted patches for those 4.7.x porting issues so we can add a DRUPAL-4-7 branch
i went on a rampage and decided to tackle this. the interested reader is encouraged to review the following 4 issues/patches: http://drupal.org/node/40661 http://drupal.org/node/40660 http://drupal.org/node/68274 http://drupal.org/node/98457 the only way to get to the UI for #40660 is to either a) know the full URLs or b) just apply #40661 (since it fixes the admin/database overview page which provides all the links). all 4 patches apply independently of each other, but if you want a fully working 4.7.x port, you need all 4. i had to do some major surgery for the FAPI conversion. however, i didn't go through the whole module, line by line, to audit for problems -- i was just trying to fix the known-bugs. so, there are still some missing t(), some improper theme() related stuff, some places it's looking at $_POST directly when it probably shouldn't be, and some highly scary direct SQL. however, all of the scary SQL stuff is within the admin interface, and that's all a big UI for running queries directly... so the SQL injection the admin could do to herself isn't really a threat we have to be worried about on a page that lets them type in whatever query they want into a nice textfield. ;) that said, i'd still like to take another look at all of this sometime when it's not 3:30am, and any other security-minded developers would be welcome to join me in auditing this highly powerful (and therefore dangerous) module. anyway, i believe those 4 patches are all that stands in the way of a DRUPAL-4-7 branch for dba.module. unless there are major objections or someone finds problems in my patches in the next 24 hours or so, i'm planning to commit everything, add the branch, make a DRUPAL-4-7--1-0 release tag, and create a 4.7.x-1.0 release node for it. thanks, -derek
On Nov 19, 2006, at 3:38 AM, Derek Wright wrote:
unless there are major objections or someone finds problems in my patches in the next 24 hours or so, i'm planning to commit everything, add the branch, make a DRUPAL-4-7--1-0 release tag, and create a 4.7.x-1.0 release node for it.
and just in the nick of time, jeremy resurfaced in the dba issue queue to review all my patches and set them to RTBC. ;) the 4.7.x-1.0 release of dba is now out: http://drupal.org/node/98518 let the masses rejoice. ;) -derek
Hi Omar, On Thu, 16 Nov 2006 17:59:27 +0200 "Omar Abdel-Wahab" <owahab@gmail.com> wrote:
Sime: I contacted him and he replied at first instantenousely then I sent him more info about my module but he didn't reply for about 10 days.
It would appear your followup message got eaten by my spam filter -- can you resend? I'll be looking for it. Derek Wright just put in a surge of effort (thank you!!) and got the dba module fully functional with Drupal 4.7 it was branched yesterday. Getting it working with 5.0 is the next step... I've personally been traveling for far too many months, but am settling down for a few months next week and hope to shake the dust from my long abandoned modules, including the dba module.
Kieran: 1. I won't release until I get a reply from Jeremy. 2. I have some features like: -- scheduled backups -- you can define multiple backup locations like: -- have them sent to your e-mail
The dba module does this, too.
-- mirror your db to another mysql server to a specific db or create a new db for every backup
Interesting. A patch for this functionality would likely be accepted.
-- stored on remote FTP
Again, a patch for this functionality would likely be accepted.
-- a folder under files/ in your drupal
Are you sure you want your entire database accessible like that? Technically you could do this with the dba module, by setting the server backup path to within files/, but I wouldn't recommend it.
-- you can have the module trying all possible locations until successful or have it sending the backup to all locations
The dba is basically all or nothing -- check boxes for which you want it to do.
-- you can maintain a certain count of backups
The dba module just keeps making backups. They have unique timestamps, so old backups are retained. It does not handle cleaning up old outdated backups for you. You can also perform live-backups. Select one, several or all tables and click 'backup', and a file will be instantly streamed to your browser which you can save to your local computer.
and I donno whether database admin module is offering those features.
Awaiting your feedback.
The biggest missing feature IMO is support for backing up Postgres databases, at this time the backup functionality is MySQL specific only. Anyone who uses Postgres and is interested in the challenge, patches would be very welcome! The entire module could use some love -- it started as a proof of concept and has some rather ugly code. And I'd love to get someone interested that could improve the user interface. If you decide to contribute to the project, please submit smallish patches that each focus on only one feature or bug. Submitting a massive patch that adds multiple features is less likely to get a proper review, and even less likely to be merged. Cheers, -Jeremy
participants (7)
-
Derek Wright -
Ian Ward -
Jeremy Andrews -
Kieran Lal -
Omar Abdel-Wahab -
Robert Douglass -
Sammy Spets