My name is Yuriy. I'm working for the small outsourcing company in Ukraine (startup) - we create web applications using Drupal CMF (http://www.webitservice.com)
I've created for my needs a Drupal module that helps me a lot during usual maintaining web site from dev environment to production server. I could not find module with similar functionality that is why developed it by my self.
I named it - MySQL DB Dump.
Overview.
My test/dev env is located on my local desktop. When I want to add some new features to the web site that is already in production - I develop and add new modules on my dev env. Then I use MySQL DB Dump for easy and fast upgrading my new features to the production server.
SVN repository:
http://code.google.com/p/drupalmysqldumpdb/
Download:
http://drupalmysqldumpdb.googlecode.com/files/mysqldumpdb.tar
Mirror:
http://www.webitservice.com/files/mysqldumpdb.tar
In latest version were fixed style issues mentioned by your team.
Steps are:
1. login as administrator on my dev box, goto the admin section of MySQL DB Dump and select one of three options(full database dump, update database dump, update database dump no content) and press submit - as a result SQL file of the tables (structure and data) is stored in the drupal root directory.
2. Then I perform svn commit - I commit all changed files and update_database_dump.sql as well.
3. I go to my server account using ssh and perform svn update.
4. I run special update_database_dump.sh file which logins into mysql and runs update_database_dump.sql - now I check by url that everything is ok.
Of course there is nothing complicated in this module it uses mysqladmin tool to generate dump of the db - but it helped me to automate this process - easy install of new web application version.
My motivation is simple - I want to share my module to be helpful for others developers and hope that link from drupal.org to my site will help me to increase PR of my startup (Drupal offshore development) - as I am using this module by myself - of course I will be maintaining it.
Thank you for Drupal!
Best regards,
Yuriy
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | mysqldumpdb.tgz | 3.51 KB | lemberg |
Comments
Comment #1
lemberg commentedComment #2
lemberg commentedComment #3
Anonymous (not verified) commentedHello, and thanks for applying for a CVS account. I am adding the review tags, and some volunteers will review your code, pointing out what needs to be changed.
Comment #4
zzolo commentedI have not looked at the code yet, but I think some basic discussion on other modules is needed up front:
* How does this differ from Backup and Migrate?
* How does this differ from a Drush-centered workflow? Drush allows you to do alot of this stuff. Maybe this could be just a Drush command.
* Are you using Drush in your shell script?
Also, storing SQL dumps in the Drupal directory seems a little insecure.
Comment #5
avpadernoThe previous application was #604736: lemberg [lemberg].
Comment #6
lemberg commentedHello.
Thank You very much for pointing those modules - I don't remember why I was not using in my dev Backup and Migrate module, and switched to develop my own solution - seems to me it had not fit my needs at that time.
Now I reviewed B&M module - it looks like my module is obsolete - with B&M module you can tune the profile to have similar functionality to update with new features site that is already in production (to exclude such tables like users, etc ...)
The only difference is that I've already prepared some pattern for such update option - it can help a newbie. Also I've added TRUNCATE of the CACHE tables - I have not found such functionality in B&M.
The reason why I put sql dump into drupal directory - for convinience - to track it through SVN with other changes in source code:
For example - you've added new module (feature) - then you commit to SVN src files and dump of MySql DB - then do svn update on production and run sql dump file. In case your changes will break something - you can easily rollback you new feature (do svn update to the previous version and run Mysql dump file).
As a summary looks like my module is not for contributing - in case some my ideas will be useful I'll contact with B&M developers and offer to extend their module.
Thank you ver much
Comment #7
lemberg commentedI think this issue can be closed as similar module exists
Comment #8
zzolo commentedI encourage you to keep writing modules and apply again with another. But yeah, closing this application.
Comment #9
lemberg commentedComment #10
avpaderno