Just wanted to announce my version of a drupalgive page. I'm continually trying to broaden my Drupal development skills and increase involvement and contributions to the open source community. I'm hoping this page highlights some of this and makes it easier for me to show my part in contributing to the Drupal project.
This has come in handy once or twice when comparing enabled modules on two different servers.
drush pm-list --status=enabled --type=module --pipe > ../pm-list-enabled.txt
drush pm-list --status=enabled --type=module --pipe > ../pm-list-enabled-othersite.txt
diff pm-list-enabled.txt pm-list-enabled-othersite.txt
I've begun adding this to each of my local D7 sites. I include this global settings file so I can edit just one $conf array. It works okay.
If an override is needed for a particular site, place it after the include for the site that needs it, or just skip the include.
At Classic, some developers are standardizing the way they sync their local development environments with remote testing servers. I recently invested time re-familiarizing myself with drush aliases. I am documenting the process in hopes of simplifying the steps for others.
Here’s the typical workflow beforehand:
- ssh into remote server
- Backup test server database by some means
- Copy and restore database backup in step #2 to local environment
- Run a set of commands, a bash script, or some such to do one, or any of the following:
- clear cache
- sanitize user logins/emails
- disable modules specific to test server environment
- enable modules specific to, or aiding, your local development environment
- Begin feature development
Using drush aliases and the the sync enable command, we can simplify the process to one step:
$ drush sql-sync @mysite.mysite-test @mysite.mysite-local -y