My name is Yuriy Asyutin. 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
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.41 KB | lemberg |
Comments
Comment #1
lemberg commentedComment #2
lemberg commentedComment #3
avpadernoThose lines need to be removed, as they are added from the packaging script.
Remove any debug code.
Comment #4
avpadernoThere have not been replies from the OP in the past 7 days. I am marking this report as .
Comment #5
avpadernoPlease read the following links as this is very important information about CVS applications.