The WET Distribution now uses Drush Make for rapid built out of the Drupal codebase. A drush make file is similar to "ant script" which allows for us to just host the code that we are developing (Installation Profile and Custom Modules, Features, and Themes) on GitHub. Any user who has Drush installed can then query this GitHub repository at the specified make file location (steps outlined below) and can then perform a build out of both the Drupal Core package + and various Contributed Modules hosted on Drupal.org.
Should you require more information not discussed in this README file please proceed to our wiki pages which offer some more information about this Drupal Distribution. The wiki pages will be constantly updated as work progresses.
You can access the Wiki here: Wiki Documentation
If you do not wish to perform a build out of Drupal yourself (instructions below) we have two options for you:
- [Virtual Machine (Vagrant Chef Provision)] (https://github.com/sylus/wet-boew-drupal-devops)
- a) A preconfigured lightweight, reproducible, and portable virtualized development environment
- Drupal Pre-Built (Currently Offline)
- a) A prebuilt (post make) codebase for people who don't want to play around with Drush
- Ensure you have the appropriate base requirements setup for Drupal as per the System Requirements documentation.
- Install Drush 5.4 or higher (inlcudes Drush Make):
- a) Linux, Mac OSX: Follow instructions at http://drupal.org/node/477684
- b) Windows: http://drush.ws/drush_windows_installer
- Install Git 1.7.10 or higher (Some lower versions of git do not apply patches from the make file with Drush Make):
- a) Linux, Mac OSX: http://code.google.com/p/git-osx-installer/
- b) Windows: http://msysgit.github.com/
- Build the complete Drupal installation software profile in your Web Server DOCROOT using the following commands on the Git Bash command prompt.
git clone https://github.com/wet-boew/wet-boew-drupal.git profiles/wetkit;
Command: drush make --prepare-install --no-gitinfofile --working-copy profiles/wetkit/build-wetkit.make <directory_name> -v --debug Example: drush make --prepare-install --no-gitinfofile --working-copy profiles/wetkit/build-wetkit.make --yes
- To quickly install using the Drush command line, change to the directory where Drupal (for example /var/www/html) was installed and enter this command. Be sure to use a password that meets the password policy for WET.
Command: drush si wetkit wetkit_wetboew_selection_form.theme=wetkit_adaptivetheme --sites-subdir=<domain> --db-url=mysql://<username>:<password>@<domain>:<port>/<database> --account-name=<username> --account-mail=<accountemail> --account-pass=<userpassword> --site-mail=<siteemail> --site-name=<sitename> Example: drush si wetkit wetkit_wetboew_selection_form.theme=wetkit_adaptivetheme --sites-subdir=drupal_wet --db-url=mysql://drupalusr:drupalusr_pass@localhost:3306/wetkit_db --account-name=admin --account-pass=WetKit@2012 [email protected] [email protected] --site-name="Web Experience Toolkit"
- Fix Permissions On files directory served by Web Server: Depending on your server set-up you will have to make sure that the /sites/default/files or /sites/<domain>/files directory has the correct owner (webserver):
chown -R apache:apache /sites/<domain>/files
NOTE: When using Mac OSX all the commands can be done directly in Terminal. When using Windows, two different command prompts are used (Not to be confused with the Windows Command Prompt. Step 4 is run in Git Bash Command Prompt and step 5 is run in the Drush command prompt).
Drush Make can also be used to update an existing install without replacing additional files. (IMPORTANT: However Drush Make will replace all files that Drush Make knows about!)
Switch (cd) to your working Drupal Directory.
To quickly update an existing site using the Drush command line, change to the directory where Drupal was installed and enter this command.
Command: drush make --no-gitinfofile --working-copy https://raw.github.com/wet-boew/wet-boew-drupal/master/build-wetkit.make .
- Since we are just updating an site instead of using drush si we will instead just update the database to reflect any changes in the code.
Command: drush -l http://<domain>:8082 updatedb Example: drush -l http://<domain>:8082 updatedb
- To get around the Proxy all you have to do is edit/create the following files that come native to the environment.
- a) Linux, Mac OSX: .curlrc
> --proxy <domain>:<port> > --proxy-user <username>:<password>
- b) Windows: _curlrc
> --proxy <domain>:<port> > --proxy-user <username>:<password>
To facilitate Drupal's automatic update and App functionality you must enable HTTP proxy support in Drupal itself, after building and installing Drupal, modify the following lines in your settings.php file.
$conf['proxy_server'] = 'www.proxyserver.ca';
$conf['proxy_port'] = 80;
$conf['proxy_username'] = '';
$conf['proxy_password'] = '';
$conf['proxy_exceptions'] = array('127.0.0.1', 'localhost');
Note that the drush installation process will enable "clean" URLs. In other words, your site will generate URLs that look like this: http://mysite.com/page rather than this: http://example.com/?q=page. However, if mod_rewrite has not been enabled for your Apache server, clean URLs will not work correctly. You can disable clean URLs for your site on this page: http://example.com//?q=admin/config/search/clean-urls. For more information, see the Clean URLs page in the Drupal documentation: http://drupal.org/getting-started/clean-urls.
The user login page is at http://example.com/?q=user or http://example.com/user (with clean URLs). You will need to input the user name and password that you provided in the installation procedure above.
This distribution borrows a substantial amount from the Panopoly Project on drupal.org due to its amazing UX features and overall architecture. If you do not need a multilingual and/or government branded site with WET integration you are encouraged to take a look at: Panopoly.