scor / dgb Goto Github PK

Hi buddy,
It just puts me "1" as commit messages when doing something like drush @dev dgb-backup --m "test commit message" Any hints of that?

Can I just do drush @dev dgb-dump
and git commit -a -m "test commit message" <- this way it seem to work for me.

Where is this bug coming from? Is my drush version to old?

By the way do you have a suggestion how to do my stage/production deployments?

Since now I used drush db- and folder sync modes. Still would like to use git or dgb. Maybe doing one repo for live and one for stage? Whats your opinion on this

thanks in advance and kind regards,

Shnifti

Hi,

It looks like dgb-dump isn't compatible with Drush 4. I'm using Drush 4.1. When I try to to do a dgb-commit or dgb-dump, I get a mysqldump error: "Warning: mysqldump: ignoring option '--databases' due to invalid value". This happens with both Drupal 6 and Drupal 7.

Any thoughts about what might be causing this incompatibility?

Cheers,
Michelle

When I try dgb-backup an error stating the command cannott be found is displayed. How do I install dgb-backup into the list of drush commands? I am trying to follow intructions below as explained in the DGD7 book, page 45.

Some functions have been forked from Drush due to the lack of flexibility of Drush (SQL) API. see details at http://drupal.org/node/698264 - Once this issue is solved, we could get rid of functions like drush_dgb_build_dump_command() and friends.

add .gitignore in order to not backup temporary/cache files and drush module backups (drupal/backup/*)

Hi,

I'm trying to install the tool just following the guidelines into the read me file.
There are several things that are not clear and, probably for this reason, the tool doesn't work at all.
I am working on Mac OS X and my Drush CLI is correctly installed and working fine ( for example with Omega Sub-theme generation ).
The READ ME file jumps from point 3 to point 6... ( Maybe I am missing something on point 4 and 5? )
I didn't understand where to create the directory dgb_instance ( or whatever since the name of the folder doesn't metter )..

I made it under /User/Myusername/dgb

Then I copy the files downloaded from Git repo into /User/Myusername/dgb where I created the .git, databases and drupal folders.
After that I put the entire drupal project files of my web public folder into /User/Myusername/dgb/drupal/

So, into the web public folder ( in my case /Library/WebServer/Documents/myDrupalProject/ ) I run the command drush dgb-backup but seems drush can't find the command.

What I missed?

Disclosure: I have no idea what I'm doing.

I have Drupal and Git up and running on my local machine (WAMP), but when trying to use drush dgb-dump from my root Drupal directory, I get the error message:
mysqldump: Can't create/write to file '../databases/default.sql' (Errcode: 13)

Which I find odd, because I can use straight up mysqldump or drush sql-dump to write to that directory and filename.

I look at the full command DGB is spitting out in my drush prompt, and notice a semi-colon and a repeat of "mysqldump". Here's what I get, with names changed:

C:\wamp\www\repo\sitename>drush dgb-dump
Dump command:
mysqldump --result-file ../databases/default.sql --single-transaction --opt -Q databasename --host=localhost --user=username --password=longpassword --skip-extended-insert --order-by-primary --ignore-table=databasename.cache --ignore-table=databasename.cache_block --ignore-table=databasename.cache_bootstrap --ignore-table=databasename.cache_field --ignore-table=databasename.cache_filter --ignore-table=databasename.cache_form --ignore-table=databasename.cache_image --ignore-table=databasename.cache_menu --ignore-table=databasename.cache_page --ignore-table=databasename.cache_path --ignore-table=databasename.flood --ignore-table=databasename.history --ignore-table=databasename.search_dataset --ignore-table=databasename.search_index --ignore-table=databasename.search_node_links --ignore-table=databasename.search_total --ignore-table=databasename.sessions --ignore-table=databasename.watchdog; mysqldump --no-data --single-transaction --opt -Q databasename --host=localhost --user=username --password=longpassword --skip-extended-insert --order-by-primary cache cache_block cache_bootstrap cache_field cache_filter cache_form cache_image cache_menu cache_page cache_path flood history search_dataset search_index search_node_links search_total sessions watchdog >> ../databases/default.sql

mysqldump: Can't create/write to file '../databases/default.sql' (Errcode: 13)

I don't know if this is intended behaviour (error aside), but I copied the code out, and ran the first half (up to the semi-colon) and the second half separately, and both created ../databases/default.sql with no problems. Together, Errcode: 13.

Is this dump command what DGB is supposed to produce? Any ideas why I can use sqldump but not DGB?

In the README.txt it says "dgb will require a drushrc.php in DRUPAL_ROOT no matter what", but according to the Drush 5 documentation, Drush 5 doesn't look for a drushrc.php in DRUPAL_ROOT anymore. Could you please update the documentation accordingly? The alternative would be to put drushrc.php in sites/all/drush/drushrc.php

$ drush dgbsql-dump
Could not find a Drupal settings.php file at ./sites/default/settings.php.
Command dgbsql-dump needs a higher bootstrap level to run - you will need invoke drush from a more functional Drupal environment to run this command.